Service use method and device, storage medium, controller and vehicle

Abstract

The invention relates to a service using method and device, a storage medium, a controller and a vehicle, and the method comprises the steps: firstly obtaining pre-configured calling information in cloud services, and then sequentially initiating calling operation to a first cloud service and a second cloud service based on the calling information of the cloud services, the method comprises the steps of determining a first successfully called current service and using business configuration of the current service, then executing calling operation in a preset period, receiving a switching identifier returned by the current service, finally switching the current service to a successfully called target service based on the switching identifier, and using business configuration of the target service. Wherein the cloud service comprises a first cloud service with a basic function and a second cloud service with an advanced function. Therefore, efficient and smooth switching use among different cloud services can be realized.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a service use method, device, storage medium, controller and vehicle. Background Art

[0002] At present, due to business qualifications and time constraints, overseas car apps are often launched quickly to provide emergency basic cloud services in the early stage of their launch. After preparing advanced cloud services with better performance, the industry generally upgrades the car apps through OTA and pushes the app version adapted to the advanced cloud services to users, thereby switching to the advanced cloud services.

[0003] However, the production of OTA upgrade packages is complicated. Due to the large number of overseas apps and various versions, compatibility and hardware adaptation must be taken into account. The release cycle is long, which seriously slows down the switching process. In addition, some users ignore OTA upgrades, resulting in a large number of car computers being unable to update and difficult to switch to advanced cloud services. Summary of the invention

[0004] The embodiment of the present application provides a service usage method, which can achieve efficient and smooth switching between different cloud services to at least partially solve the above technical problems.

[0005] In order to achieve the above-mentioned purpose, according to the first aspect of the present application, a service using method is provided, comprising:

[0006] Obtaining pre-configured call information in a cloud service; the cloud service includes a first cloud service with basic functions and a second cloud service with advanced functions;

[0007] Based on the call information of the cloud service, initiating call operations to the first cloud service and the second cloud service in sequence, determining the first successfully called current service and using the business configuration of the current service;

[0008] Execute the calling operation at a preset period, and receive a switching identifier returned by the current service;

[0009] The current service is switched to the successfully called target service based on the switching identifier, and the service configuration of the target service is used.

[0010] Optionally, the calling information includes a calling sequence and a region identifier of the cloud service, and the acquiring the calling information pre-configured in the cloud service includes:

[0011] Obtaining calling priorities of multiple preset domain names of the cloud service;

[0012] Determining a calling order of the cloud services based on a calling priority of each of the preset domain names;

[0013] Based on the region where the cloud service is located, the region identifier of the region is used as the region identifier of the cloud service.

[0014] Optionally, the initiating calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service to determine the current service that is first successfully called includes:

[0015] In response to the call operation initiated to the first cloud service, receiving a first version identifier returned by the first cloud service;

[0016] When the first version identifier satisfies a first preset condition, it is determined that the first cloud service is successfully called and the first cloud service is used as the current service.

[0017] Optionally, the initiating calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service to determine the current service that is first successfully called further includes:

[0018] When the first version identifier does not meet the first preset condition, initiating a call operation to the second cloud service, and receiving a second version identifier returned by the second cloud service;

[0019] When the second version identifier satisfies a second preset condition, it is determined that the second cloud service is successfully called and the second cloud service is used as the current service.

[0020] Optionally, the initiating calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service to determine the current service that is first successfully called further includes:

[0021] When the second version identifier does not satisfy the second preset condition, the stored local service is determined as the current service.

[0022] Optionally, the call information also includes a request version identifier for requesting to call the target version cloud service, wherein:

[0023] Optionally, the method further comprises:

[0024] Obtain a first version of the cloud service corresponding to the first version identifier, and a second version of the cloud service corresponding to the second version identifier;

[0025] The first preset condition includes that the release time of the first version is after the release time of the requested version of the requested version identifier, and the first version identifier is different from the switching identifier;

[0026] The second preset condition includes that the release time of the second version is after the release time of the requested version, and the second version identifier is different from the switching identifier.

[0027] Optionally, the switching the current service to the successfully called target service based on the switching identifier includes:

[0028] When receiving the switching identifier returned by one of the first cloud service or the second cloud service, initiating a call operation to the other of the first cloud service or the second cloud service;

[0029] When the calling operation satisfies a third preset condition, determining the other of the first cloud service or the second cloud service as the target service;

[0030] When the calling operation does not satisfy the third preset condition, the local service is determined as the target service.

[0031] Optionally, the method further comprises:

[0032] Get the total number of calls when the calling operation is successfully executed;

[0033] If the total number of calls is less than a preset threshold, determining that the call operation meets the third preset condition;

[0034] If the total number of calls is greater than or equal to the preset threshold, it is determined that the call operation does not meet the third preset condition.

[0035] Optionally, the switching the current service to the successfully called target service and using the service configuration of the target service further includes:

[0036] When an exception occurs to the target service, a preset number of call operations are performed on the target service;

[0037] If the target service is successfully called within the preset number of times, the service configuration of the target service is used;

[0038] If the target service is not successfully called within the preset number of times, the calling operation of the current service is skipped and the business configuration of the local service is used.

[0039] According to a second aspect of the present application, a service using device is provided, including:

[0040] An information acquisition module, used to acquire pre-configured call information in a cloud service; the cloud service includes a first cloud service with basic functions and a second cloud service with advanced functions;

[0041] A service calling module, configured to initiate calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service, determine the first successfully called current service, and use the business configuration of the current service;

[0042] An identification receiving module, used to perform the calling operation at a preset period and receive a switching identification returned by the current service;

[0043] The service switching module is used to switch the current service to the successfully called target service based on the switching identifier, and use the business configuration of the target service.

[0044] According to a third aspect of the present application, a computer-readable storage medium is also provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the service use method described above are implemented.

[0045] According to a fourth aspect of the present application, a controller is also provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the service use method as described above are implemented.

[0046] According to a fifth aspect of the present application, a vehicle is also provided, comprising the controller as described above.

[0047] According to a sixth aspect of the present application, a computer program product is also provided, comprising a computer program or instructions, which, when executed by a processor, implement the steps of the service usage method as described above.

[0048] To sum up, in the embodiments of the present application, through the above-mentioned technical scheme, the pre-configured calling information in the cloud service can be obtained first, and the vehicle computer end can subsequently directly call the required cloud service based on the calling information. The vehicle computer end only needs to switch between the basic cloud service and the advanced cloud service through the above-mentioned calling operations, without relying on and waiting for the vehicle computer end to perform OTA upgrades, so that the vehicle computer end can realize efficient and smooth switching between different services.

[0049] Other features and advantages of the present application will be described in detail in the subsequent specific implementation section. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can obtain other drawings based on these drawings without creative work.

[0051] In order to more completely understand the present application and its beneficial effects, the following description will be given in conjunction with the accompanying drawings, wherein the same figure numbers represent the same parts in the following description.

[0052] Figure 1 is a flowchart of a method for using a service provided in an exemplary embodiment of the present disclosure;

[0053] Figure 2 is a switch provided in an exemplary embodiment of the present disclosure;

[0054] Figure 3 is a schematic diagram of data interaction between a vehicle terminal, a first cloud service, and a second cloud service provided in an exemplary embodiment of the present disclosure;

[0055] Figure 4 is a schematic diagram of a vehicle-side initialization calling a cloud service provided in an exemplary embodiment of the present disclosure;

[0056] Figure 5 is a schematic diagram of a vehicle terminal switching from a first cloud service to a second cloud service provided in an exemplary embodiment of the present disclosure;

[0057] Figure 6 is a schematic diagram of a vehicle terminal switching from a second cloud service to a first cloud service provided in an exemplary embodiment of the present disclosure;

[0058] Figure 7 is a schematic diagram of a service using device provided in an exemplary embodiment of the present disclosure;

[0059] Figure 8 Schematic diagram of the architecture of a vehicle provided in an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0060] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0061] Based on the problems mentioned in the above background technology, in the relevant technology, in the operation process of overseas car-side car apps, the current practice generally adopted by the industry is that when the car app goes online, it is subject to conditions such as business qualifications and online time. An emergency cloud service, namely the basic cloud service, will be urgently launched in the initial stage. Later, as the business develops, we will start planning advanced cloud services with more powerful functions, higher security and greater autonomy. After the advanced cloud service is fully prepared and reaches a mature and available state, it is expected that the background of the car app docking will be fully converted from the basic cloud service to the advanced cloud service. The conventional way to achieve this conversion is to use the car OTA upgrade mechanism, that is, to push the updated car app version that has been adapted to the advanced cloud service to the user through OTA upgrade, and the user will download and install it to complete the switch of the cloud service.

[0062] However, the OTA upgrade of car machines faces various difficulties. For example, there are a large number of overseas car machine apps, and each app has a variety of version branches, which makes the production process of OTA upgrade packages extremely complicated. Not only must the compatibility of different app versions with the new cloud service be considered, but also the adaptability of different car machine hardware platforms and many other factors must be taken into account. At the same time, the release cycle of OTA upgrade packages is long, usually taking 6-24 months. In addition, some users often ignore or do not use OTA upgrades, which greatly delays the process of cloud service switching. In addition, in the actual switching process of cloud services, unexpected situations often occur due to many uncertain factors such as complex network environment and software compatibility. When encountering such emergencies, traditional practices lack effective response measures and cannot easily and quickly switch the current cloud service back to the original cloud service in a stable state, making it impossible for the car machine to be used normally, and related business operations are seriously disturbed, making it difficult to control the negative impact caused by accidents to a minimum.

[0063] In order to solve the above existing technical problems, this application provides a service usage method, please refer to Figure 1 The service usage method provided in the embodiment of the present application includes steps S101-S104, which are described in detail below.

[0064] Step S101: Obtain the call information pre-configured in the cloud service.

[0065] In the scenario of the present application, the caller of the cloud service can be a car app on the car side. For example, the car app can be an app adapted for the navigation, map, smart driving, voice broadcast, etc. of the vehicle. The above car app can be run by calling the function of the cloud service.

[0066] In some embodiments, the cloud service may include a first cloud service with basic functions and a second cloud service with advanced functions. For the convenience of distinction and description, the first cloud service may also be referred to as "cloud service S1" and the second cloud service may also be referred to as "cloud service S2".

[0067] The first cloud service can be the basic cloud service used in the initial stage of the launch of the car-machine app. For example, it can be a service developed by the car-machine development company itself, or it can be a service provided by a qualified third-party supplier. It is mainly to meet the urgent business needs when the car-machine app is launched and play an initial transition role.

[0068] Correspondingly, the second cloud service can be an advanced cloud service that is more robust, more secure, and more autonomous than the first cloud service. It is usually planned and matured after the first cloud service. The second cloud service can be understood as an upgraded and replaced service for the previous first cloud service. It can be used as the main cloud service for the car app to connect to in the later stage, and is used to improve the service quality and performance of the car app.

[0069] Among them, the call information may include the call order and regional identification of the cloud server. Specifically, each cloud service is configured with a corresponding global domain name. For example, the global domain name N1 of the first cloud service is xx.com, and the global domain name N2 of the second cloud service is xxx.com. Setting a global domain name can facilitate the car terminal to access the corresponding cloud services worldwide. Usually, the domain names of each cloud service can be built-in before the car app is released, so that no matter in which region, you can request to call the required cloud service through the domain name when the network connection is normal.

[0070] In some embodiments, cloud services may be called in a preset calling order, and the preset calling order may be determined based on the priority or business policy of each cloud service. For example, in most cases the vehicle terminal will first try to call the basic first cloud service.

[0071] The region identifier can be a region code composed of numbers, letters or characters, and can be used to mark different regions where the vehicle terminal is located, such as A1, B1, etc. Through the region code, the vehicle app can determine which cloud service and corresponding business version should be called in the region, thereby helping to ensure that the vehicle app obtains appropriate cloud services in accordance with local laws and regulations and business needs.

[0072] In some embodiments, step S101 may include:

[0073] First, obtain the calling priorities of multiple preset domain names of the cloud service;

[0074] Next, based on the calling priority of each preset domain name, the calling order of the cloud service is determined;

[0075] Finally, based on the region where the cloud service is located, the region identifier of the region is used as the region identifier of the cloud service.

[0076] In a specific implementation, in order to ensure a smooth transition of cloud service functions, the calling priority of the preset domain name corresponding to the first cloud service is usually higher than the calling priority of the preset domain name corresponding to the second cloud service. In some embodiments, the calling priority can also be set based on multiple factors such as business needs, network conditions, and service stability. For example, if the cloud service node corresponding to a preset domain name has better network connection quality and faster response speed in the area, then the domain name can be given a higher calling priority.

[0077] In some embodiments, the car app can determine the calling order of the cloud service according to the calling priority of the preset domain name set previously, for example, it can try to use the preset domain name to access the corresponding cloud service in order from high to low priority. Assuming that cloud service S1 corresponds to preset domain name N1, cloud service S2 corresponds to preset domain name N2, and the calling priority of preset domain name N1 is greater than that of preset domain name N2, cloud service S1 can be called through preset domain name N1 first. If the preset domain name N1 cannot be successfully connected, cloud service S2 can be called through preset domain name N2.

[0078] In overseas business scenarios, different regions have different regulatory requirements and business characteristics. In order to ensure that the car app can obtain cloud services in compliance and accurately, it is necessary to clarify the correspondence between cloud services and regions. For example, if the cloud service is located in region A, then the region ID corresponding to region A can be A1 or A2. For example, if the cloud service is located in region B, then the region ID corresponding to region B can be B1 or B2, etc.

[0079] It should be noted that before executing step S101, Figure 3 As shown, the public IP of cloud service S1 can be added to the global domain name N1 first. In this way, when the car app accesses it through the domain name N1, the domain name resolution system can resolve N1 to the public IP address of cloud service S1, thereby establishing a connection between the car app and cloud service S1, so that the car app can obtain various functions and data provided by cloud service S1.

[0080] In the scenario of this application, salespeople at different cloud service development ends can configure cloud service related parameters. For example, salespeople can set the region codes supported by cloud service S1 to A1 and B1, and set the service version numbers to A1-V1.1 and B1-V1.1, respectively, to represent the V1.1 cloud service in region A1 and the V1.1 cloud service in region B1. When the version number is not set, the default value of the version number is V0.1.

[0081] After the above configuration operations, the vehicle app can obtain the call information through the operation of step S101 above. Figure 3 As shown, when the car app is installed or OTA upgraded, the global domain name N1 of cloud service S1 and the global domain name N2 of cloud service S2 can be obtained and built-in. In this way, when the car app is started or needs to interact with the cloud service, it can directly determine which domain names to access the corresponding cloud service.

[0082] Step S102: Based on the calling information of the cloud service, initiating calling operations to the first cloud service and the second cloud service in sequence, determining the first successfully called current service and using the business configuration of the current service.

[0083] Specifically, Figure 2 As shown, after obtaining the calling information of the cloud service, the car app can call the cloud service according to a preset period. For example, the preset period can be each time the car starts or every half an hour. This preset period can also be dynamically adjusted in the business configuration parameters of the cloud service. The first cloud service can be called first. If the call is successful, the first cloud service is set as the current service, and the business configuration of the first cloud service is used. Correspondingly, if the call fails, the call is switched to the second cloud service. If the call is successful, the second cloud service is set as the current service, and the business configuration of the second cloud service is used. Similarly, if the call fails, it switches to calling the first cloud service until the call is successful.

[0084] In some embodiments, the call information may also include a request version identifier for requesting to call a target version cloud service.

[0085] In some embodiments, step S102 may include:

[0086] First, in response to a call operation initiated to a first cloud service, a first version identifier returned by the first cloud service is received;

[0087] Next, when the first version identifier satisfies the first preset condition, it is determined that the first cloud service is successfully called and the first cloud service is used as the current service. Correspondingly, when the first version identifier does not satisfy the first preset condition, a call operation is initiated to the second cloud service, and a second version identifier returned by the second cloud service is received;

[0088] Finally, when the second version identifier satisfies the second preset condition, it is determined that the second cloud service is successfully called and the second cloud service is used as the current service.

[0089] Specifically, in the initialization stage when the car-machine app periodically refreshes the business configuration, after the car-machine app requests to call the cloud service, the cloud service can return a version identifier to the car-machine app. The version identifier can be the version number of the cloud service, such as V1.1, V1.2, etc., to determine whether the current version of the cloud service meets the version of the cloud service requested by the car-machine app. If the version requirements are met, the car-machine app can successfully call the cloud service and use it as the current service. Correspondingly, if the version requirements are not met, the car-machine app cannot call the cloud service.

[0090] It can be understood that if the first cloud service cannot be successfully called at present, according to the calling rules of the cloud service, the car app needs to switch to calling the next second cloud service. It can then continue to determine whether the second version identifier returned by the second cloud service meets the version requirements for a successful call. If the version requirements are met, the car app can successfully call the second cloud service and use it as the current service. Correspondingly, if the version requirements are not met, the car app cannot call the second cloud service.

[0091] In some embodiments, the first version identifier corresponding to the first version of the cloud service and the second version identifier corresponding to the second version of the cloud service may be first obtained. The first preset condition may include that the release time of the first version is after the release time of the requested version of the requested version identifier, and the first version identifier is different from the switching identifier; the second preset condition may include that the release time of the second version is after the release time of the requested version, and the second version identifier is different from the switching identifier.

[0092] Specifically, when the car app initiates a call request to the cloud service S1, it can carry an expected request version identifier, for example, the request version identifier can be A1-V1.1, indicating that the car app hopes that the cloud service S1 in the A1 region can provide a cloud service with a version identifier of A1-V1.1. If the first version identifier returned by the cloud service S1 is A1-V1.1 or a later version identifier, such as A1-V1.2, it indicates that the first cloud service has been successfully called.

[0093] Among them, the switching identifier can be a pre-set special identifier, which is used to inform the car app that the app currently requested to be called cannot be called, and it is necessary to call and switch to the next cloud service. For example, the switching identifier is V0.0. Assuming that the first cloud service returns the switching identifier, the car app should switch to calling the second cloud service and temporarily stop calling the first cloud service thereafter.

[0094] In some embodiments, when the second version identifier does not satisfy the second preset condition, the stored local service is determined as the current service.

[0095] It is understandable that since each car app may go through multiple calling operations, each successful call to a cloud service can cache the business configuration of that version of the cloud service locally as a local service. After the calls to the first cloud service and the second cloud service fail in sequence, the local service stored locally can be temporarily used as the current service. However, it should be noted that under normal circumstances, in order to ensure the stable operation of the car app, it is almost impossible that the first cloud service and the second cloud service cannot be called at the same time. Therefore, this mechanism is only used as a fallback solution to avoid the car app from failing to run in the extreme case where the first cloud service and the second cloud service cannot be called.

[0096] Step S103: Execute the calling operation at a preset period, and receive the switching identifier returned by the current service.

[0097] As mentioned above, a preset period can be flexibly set so that the car app can perform cloud service call operations at a stable frequency. In the scenario of this application, there are two situations where service switching is required. After the car app is initialized, it successfully calls the current service and uses its business configuration. For example, the current service may be the first cloud service, and it needs to switch from the first cloud service to a second cloud service with better functions. In this case, the car app can receive the switching identifier returned by the first cloud service, indicating that the first cloud service is currently unavailable and needs to switch to calling the second cloud service.

[0098] In another case, assuming that the car app has successfully called the second cloud service and used its business configuration, but during the operation of the car app, the second cloud service may have an exception causing it to be temporarily unavailable, so the car app needs to switch back to the first cloud service. In this case, the car app can receive a switching identifier returned by the second cloud service, indicating that the second cloud service is currently unavailable and needs to switch to calling the first cloud service.

[0099] In actual applications, when service switching is required, the operators of the first cloud service and the second cloud service can flexibly configure the switching identifier in the cloud service to be switched, for example Figure 3 In the scenario where the vehicle app requests to switch the first cloud service to the second cloud service, the salesperson can pre-configure the switching identifiers A1-V0.0 and A2-V0.0 in the calling information of the first cloud service. In this way, when the vehicle app subsequently obtains the calling information of the first cloud service, it can receive the switching identifier returned by the first cloud service, informing the vehicle app that the first cloud service cannot be called at present and needs to switch to calling the next second cloud service.

[0100] It should also be noted that the requested cloud service can not only return the version identifier, but also the business parameters and other configuration information of the cloud service, so that after the car app successfully calls the cloud service, it can directly use the business configuration and parameters of the cloud service for stable operation.

[0101] Through the above method, the entire process only interacts with the first cloud service and the second cloud service through the vehicle app. There is no need to rely on and wait for OTA upgrades on the vehicle side, and efficient and smooth service switching can be achieved.

[0102] Step S104: Switch the current service to the successfully called target service based on the switching identifier, and use the service configuration of the target service.

[0103] It can be understood that no matter whether the scenario is switching the first cloud service to the second cloud service or switching the second cloud service back to the first cloud service, after successfully switching and calling the related cloud service, the successfully called cloud service can be determined as the target service and the business configuration of the target service can be used.

[0104] In some embodiments, step S104 may include:

[0105] First, when receiving a switching identifier returned by one of the first cloud service or the second cloud service, initiating a call operation to the other of the first cloud service or the second cloud service;

[0106] Next, when the calling operation satisfies a third preset condition, determining the other of the first cloud service or the second cloud service as a target service;

[0107] Finally, when the calling operation does not meet the third preset condition, the local service is determined as the target service.

[0108] In some embodiments, the total number of calls when the call operation is successfully executed can be obtained first. If the total number of calls is less than a preset threshold, it is determined that the call operation meets the third preset condition; if the total number of calls is greater than or equal to the preset threshold, it is determined that the call operation does not meet the third preset condition.

[0109] Specifically, in order to prevent the car app from repeatedly calling cloud services without limit, wasting resources and time, a preset threshold for measuring the total number of calls can be set. For example, the preset threshold can be 3, which means that for each cloud service, the car app can try to perform a call operation up to 3 times. If after trying to call all cloud services and each cloud service has reached 3 times, there is still no normal response, then the car app will stop calling the operation and may take some other countermeasures, such as prompting the user that a fault has occurred, using local cached data, etc., to try to ensure that some functions of the car app can continue to be used.

[0110] In some embodiments, when an exception occurs in the target service, a preset number of call operations may be performed on the target service. If the target service is successfully called within the preset number of times, the service configuration of the target service is used; if the target service is not successfully called within the preset number of times, the call operation on the current service is skipped and the service configuration of the local service is used.

[0111] See also Figures 4 to 6 ,like Figure 4 As shown, after the car app is connected to the cloud service S1, it usually runs according to the established process. However, occasionally a small number of car apps will use the cloud service S1 to make abnormal requests. At this time, these abnormal requests will be switched to the cloud service S2 for processing. It should be noted that at this time, the car app has cached the version number of the cloud service S1 locally, and this version number is not the switching identifier used to trigger the switch. Based on this, the car app will still give priority to initiating a request to the cloud service S1 in the next request cycle. Only when N consecutive rounds, such as 5 consecutive rounds of calls to the cloud service S1, have failed, will the car app officially switch to the cloud service S2 and update the cached version number to the latest version of the cloud service S2.

[0112] like Figure 5 As shown, after the car app switches from cloud service S1 to cloud service S2, cloud service S2 will be used stably in most cases. However, there are still very rare cases where a small number of car apps can generate abnormal requests. These abnormal requests may be switched to cloud service S1 for processing. At this time, the business version number of cloud service S1 happens to be set as the switching identifier that triggers the switch. Therefore, after this round of abnormal requests finds the switching identifier of cloud service S1, it will immediately switch back to cloud service S2. In this situation, the car app will give cloud service S2 another request opportunity. If this request to call cloud service S2 still fails, the car app will no longer consider switching back to cloud service S1.

[0113] like Figure 6 As shown, for the A1 region, the request process of the car app is the same as Figure 5 The general request process presented has not changed, and the specific processing method is also the same as Figure 4 It is consistent with what is described. For the B1 region, when the car app switches from cloud service S2 to cloud service S1, only a small number of abnormal requests from the car app will be switched to cloud service S2. The reason is that the business version number of cloud service S2 has been set to the switching version number at this time, so once this situation occurs, this round of requests will immediately switch back to cloud service S1. At the same time, the car app can try to request cloud service S1 again. If the request fails, the subsequent car app will not switch back to cloud service S2.

[0114] To sum up, in the embodiments of the present application, through the above-mentioned technical scheme, the pre-configured calling information in the cloud service can be obtained first, and the vehicle computer end can subsequently directly call the required cloud service based on the calling information. The vehicle computer end only needs to switch between the basic cloud service and the advanced cloud service through the above-mentioned calling operations, without relying on and waiting for the vehicle computer end to perform OTA upgrades, so that the vehicle computer end can realize efficient and smooth switching between different services.

[0115] Figure 7 is a schematic diagram of a service usage device provided in an embodiment of the present application. Figure 7 The service using device may include an information obtaining module 201 , a service calling module 702 , an identification receiving module 203 and a service switching module 204 .

[0116] The information acquisition module 201 may be used to acquire the pre-configured call information in the cloud service; the cloud service includes a first cloud service with basic functions and a second cloud service with advanced functions;

[0117] The service calling module 202 may be used to initiate calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service, determine the first successfully called current service, and use the business configuration of the current service;

[0118] The identification receiving module 203 may be used to perform the calling operation at a preset period and receive the switching identification returned by the current service;

[0119] The service switching module 204 may be configured to switch the current service to the successfully called target service based on the switching identifier, and use the service configuration of the target service.

[0120] Among them, the information acquisition module 201, the service call module 702, the identification receiving module 203 and the service switching module 204 can be used to execute steps S101-S104 in the embodiments corresponding to the above-mentioned service usage method respectively. For the specific implementation methods of these modules and more details, please refer to the corresponding method part, which will not be repeated here one by one.

[0121] An embodiment of the present application also provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the processor is configured to execute the above-mentioned service usage method.

[0122] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0123] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0124] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0125] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0126] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0127] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0128] Computer readable media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated communication signals and carrier waves.

[0129] like Figure 6 As shown, it is a schematic diagram of the architecture of a vehicle provided in the embodiment of the present application. In this embodiment, the vehicle 400 may include a controller 300, on which a computer program is stored, and when the computer program is executed by the processor, the steps of the above service use method are implemented. In this embodiment, the vehicle may be a fuel vehicle, a plug-in hybrid vehicle, or a new energy vehicle, etc., and this disclosure does not specifically limit this.

[0130] In the description of this application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0131] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0132] The embodiments, implementation methods and related technical features of the present application can be combined and replaced with each other without conflict.

[0133] The above are only preferred embodiments of the present application and do not constitute any form of limitation to the present application. However, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present application without departing from the content of the technical solution of the present application are still within the scope of the technical solution of the present application.

Claims

1. A method for using a service, characterized in that: include: Get the pre-configured call information in the cloud service; The cloud service includes a first cloud service with basic functions and a second cloud service with advanced functions; Based on the call information of the cloud service, initiating call operations to the first cloud service and the second cloud service in sequence, determining the first successfully called current service and using the business configuration of the current service; Execute the calling operation at a preset period, and receive a switching identifier returned by the current service; The current service is switched to the successfully called target service based on the switching identifier, and the service configuration of the target service is used.

2. The method according to claim 1, characterized in that The calling information includes the calling sequence and region identifier of the cloud service, and the obtaining of the calling information pre-configured in the cloud service includes: Obtaining calling priorities of multiple preset domain names of the cloud service; Determining a calling order of the cloud services based on a calling priority of each of the preset domain names; Based on the region where the cloud service is located, the region identifier of the region is used as the region identifier of the cloud service.

3. The method according to claim 1, characterized in that: The initiating calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service, and determining the current service that is first successfully called, includes: In response to the call operation initiated to the first cloud service, receiving a first version identifier returned by the first cloud service; When the first version identifier satisfies a first preset condition, it is determined that the first cloud service is successfully called and the first cloud service is used as the current service.

4. The method according to claim 3, characterized in that The initiating calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service to determine the current service that is first successfully called also includes: When the first version identifier does not meet the first preset condition, initiating a call operation to the second cloud service, and receiving a second version identifier returned by the second cloud service; When the second version identifier satisfies a second preset condition, it is determined that the second cloud service is successfully called and the second cloud service is used as the current service.

5. The method according to claim 3, characterized in that: The initiating calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service to determine the current service that is first successfully called also includes: When the second version identifier does not satisfy the second preset condition, the stored local service is determined as the current service.

6. The method according to claim 5, characterized in that The method further comprises: Obtain a first version of the cloud service corresponding to the first version identifier, and a second version of the cloud service corresponding to the second version identifier; The first preset condition includes that the release time of the first version is after the release time of the requested version of the requested version identifier, and the first version identifier is different from the switching identifier; The second preset condition includes that the release time of the second version is after the release time of the requested version, and the second version identifier is different from the switching identifier.

7. The method according to claim 5, characterized in that The switching of the current service to the successfully called target service based on the switching identifier includes: When receiving the switching identifier returned by one of the first cloud service or the second cloud service, initiating a call operation to the other of the first cloud service or the second cloud service; When the calling operation satisfies a third preset condition, determining the other of the first cloud service or the second cloud service as the target service; When the calling operation does not satisfy the third preset condition, the local service is determined as the target service.

8. The method according to claim 7, characterized in that The method further comprises: Get the total number of calls when the calling operation is successfully executed; If the total number of calls is less than a preset threshold, determining that the call operation meets the third preset condition; If the total number of calls is greater than or equal to the preset threshold, it is determined that the call operation does not meet the third preset condition.

9. The method according to claim 5, characterized in that The switching of the current service to the successfully called target service and using the business configuration of the target service also includes: When an exception occurs to the target service, a preset number of call operations are performed on the target service; If the target service is successfully called within the preset number of times, the service configuration of the target service is used; If the target service is not successfully called within the preset number of times, the calling operation of the current service is skipped and the business configuration of the local service is used.

10. A service using device, characterized in that: include: An information acquisition module, used to obtain the call information pre-configured in the cloud service; The cloud service includes a first cloud service with basic functions and a second cloud service with advanced functions; A service calling module, configured to initiate calling operations to the first cloud service and the second cloud service in sequence based on the calling information of the cloud service, determine the first successfully called current service, and use the business configuration of the current service; An identification receiving module, used to perform the calling operation at a preset period and receive a switching identification returned by the current service; The service switching module is used to switch the current service to the successfully called target service based on the switching identifier, and use the business configuration of the target service.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

12. A controller having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

13. A vehicle, characterized in that: Comprising the controller as claimed in claim 12.

14. A computer program product, characterized in that The method comprises a computer program or instructions, which implement the steps of the method according to any one of claims 1 to 9 when executed by a processor.

Images