Scene service processing method and device, electronic equipment, storage medium and vehicle

Abstract

The application provides a processing method and device of a scene service, an electronic device, a storage medium and a vehicle; the method comprises: downloading a general scene service and a user scene service with a category identifier from a cloud platform; adding the category identifier to each user scene service; classifying the scene services according to the category identifier, and enabling or disabling each scene service according to the category, wherein the scene services comprise the general scene service and the user scene service. It can be seen that, after classifying the general scene service according to the category identifier, the method customizes the classification of the user scene service, and after the user scene service is classified into the category of the general scene service, the conflict of the execution logic can be reduced, and the user's customized demand and the robustness of the scene service in execution are taken into account.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field, and particularly relate to a scene service processing method and device, electronic equipment, storage medium and vehicle. BACKGROUND

[0002] In the related scene service processing method, the scene services are often subjectively divided according to different application scenarios, which often leads to confusion of categories, and execution conflicts between execution logics during execution of the scene services.

[0003] Therefore, there is a need for a solution that can reasonably divide different categories and reduce execution conflicts. SUMMARY

[0004] Therefore, the present application aims to provide a scene service processing method and device, electronic equipment, storage medium and vehicle to solve the problem of unreasonable category division and easy execution conflicts.

[0005] To achieve the above purpose, the present application provides a scene service processing method applied to a mobile terminal, which comprises the following steps:

[0006] downloading general scene services and user scene services with category identifiers from a cloud platform;

[0007] adding the category identifiers to each user scene service;

[0008] classifying the scene services according to the category identifiers, and enabling or disabling each scene service according to the category, wherein the scene services include the general scene services and the user scene services.

[0009] Further, the category identifiers include main category identifiers and subcategory identifiers.

[0010] The classifying the scene services according to the category identifiers comprises the following steps:

[0011] dividing the general scene services and the user scene services with the same main category identifier into the same main category;

[0012] dividing the general scene services and the user scene services with the same subcategory identifier in the same main category into the same subcategory.

[0013] Further, the enabling each scene service according to the category comprises the following steps:

[0014] in response to enabling or disabling any scene service, adjusting all other scene services in the same main category as the scene service to the same enabled or disabled state;

[0015] In response to enabling or disabling any one scene service, all other scene services of the same subcategory as the scene service are adjusted to the same enabled or disabled state.

[0016] Based on the above purpose and based on the same inventive concept, the application also provides a processing method of scene services, applied to a cloud platform, the method comprising:

[0017] According to different user permissions of the execution logic created in each scene service, all scene services are divided into common scene services and user scene services;

[0018] Among all the common scene services, the same logic script is deployed, and the common scene services in which the same logic script is deployed in the same architecture level are divided into the same category, wherein each logic script is used to deploy at least one complete non-divisible execution logic;

[0019] A category identifier is added to the common scene services belonging to the same category, and each common scene service is published to a mobile terminal together with the corresponding category identifier;

[0020] The user scene services are published to the mobile terminal.

[0021] Further, according to different user permissions of the execution logic created in each scene service, all scene services are divided into common scene services and user scene services, comprising:

[0022] It is judged whether the execution logic in each scene service supports the permission of secondary editing by a user;

[0023] In response to the execution logic not supporting secondary editing, the scene service is determined as a common scene service;

[0024] In response to the execution logic supporting secondary editing, the scene service is determined as a user scene service.

[0025] Based on the same inventive concept, the application also provides a processing method of scene services, applied to a car machine terminal, the method comprising:

[0026] Downloading scene services with preset main category identifiers and / or subcategory identifiers from the cloud platform;

[0027] Dividing scene services with the same main category identifier into the same main category, and dividing scene services with the same subcategory identifier under the same main category into the same subcategory;

[0028] In response to enabling or disabling any one scene service, all other scene services of the same main category as the scene service are adjusted to the same enabled or disabled state;

[0029] In response to enabling or disabling any one of the scene services, other scene services of the same subcategory as the scene service are all adjusted to the same enabled or disabled state.

[0030] Based on the same inventive concept, the application further provides a processing device for scene services, comprising a scene service downloading module, an identification adding module and a scene service classification module.

[0031] The scene service downloading module is configured to download general scene services and user scene services with category identifications from a cloud platform.

[0032] The identification adding module is configured to add the category identifications to each of the user scene services.

[0033] The scene service classification module is configured to classify the scene services according to the category identifications and enable or disable each of the scene services according to the categories, wherein the scene services comprise the general scene services and the user scene services.

[0034] Based on the same inventive concept, the application further provides a processing device for scene services, comprising a type dividing module, a general scene service classification module, a general scene service publishing module and a user scene service publishing module.

[0035] The type dividing module is configured to divide all the scene services into general scene services and user scene services according to different permissions of execution logic created in each of the scene services.

[0036] The general scene service classification module is configured to divide general scene services, in which the same logic scripts are deployed and the same logic scripts are deployed in the same architecture level, into the same category, wherein each of the logic scripts is used to deploy at least one complete and indivisible execution logic.

[0037] The general scene service publishing module is configured to add category identifications to the general scene services belonging to the same category and publish each of the general scene services together with the corresponding category identification to a mobile terminal.

[0038] The user scene service publishing module is configured to publish the user scene services to the mobile terminal.

[0039] Based on the same inventive concept, the application further provides an electronic device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the processing method for scene services according to any one of the above.

[0040] Based on the same inventive concept, the present application also provides a computer readable storage medium, wherein the computer readable storage medium stores computer instructions for causing the computer to execute the processing method of the scenario service.

[0041] Based on the same inventive concept, the present application also provides a vehicle, comprising a processor and a storage medium for storing computer instructions for causing the processor to execute the processing method of the scenario service applied to the vehicle terminal.

[0042] From the above, it can be seen that the processing method, device, electronic equipment, storage medium and vehicle of the scenario service provided by the present application divide the scenario service into user scenario service and general scenario service based on different permissions of the scenario service, and different category division methods are respectively performed. In the category division of the general scenario service, the series relationship of the deployed plot and script is comprehensively considered, and the category is divided according to the execution logic of each group and the hierarchical deployment, so that the general scenario service of the same category has the same or related parts in structure and function, and after the category division, the general scenario services of different categories are published to the mobile terminal by marking the category identifier, so as to realize effective classification of the scenario service, based on the same execution logic, and ensure that the general scenario services of the same category cannot be started at the same time, reducing the conflict between the execution logics. BRIEF DESCRIPTION OF DRAWINGS

[0043] In order to more clearly illustrate the technical solutions in the present application or related art, the following will briefly introduce the drawings needed to be used in the embodiments or related art descriptions. Obviously, the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

[0044] Figure 1 The first flowchart of the processing method of the scenario service of the embodiment of the present application;

[0045] Figure 2 The second flowchart of the processing method of the scenario service of the embodiment of the present application;

[0046] Figure 3 The first structure schematic diagram of the processing device of the scenario service of the embodiment of the present application;

[0047] Figure 4 The second structure schematic diagram of the processing device of the scenario service of the embodiment of the present application;

[0048] Figure 5 The structure schematic diagram of the electronic equipment of the embodiment of the present application. DETAILED DESCRIPTION

[0049] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0050] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed following the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0051] It is understood that before using the technical solutions of the various embodiments in this disclosure, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.

[0052] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations of this disclosed technical solution.

[0053] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0054] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0055] As described in the background section, the processing methods for related scenario services are still difficult to meet the needs of actual use.

[0056] The applicant finds that the main problem of the related scene service processing method is that the processing method of the related scene service is often subjectively divided according to the different application scenarios, which often leads to confusion of categories, and execution conflicts between execution logics during scene service execution.

[0057] Therefore, one or more embodiments of the present application provide a scene service processing method, which processes the scene service based on the series relationship between each group of execution logics in a general scene and the interaction between the cloud platform and the mobile terminal.

[0058] In the embodiments of the present application, a vehicle equipped with a scene service is taken as a specific example.

[0059] The vehicle machine in the vehicle can be used to download, deploy, store and execute the scene service published by the cloud platform; the cloud platform in communication with the vehicle machine can create, deploy, store and operate the scene service; and the mobile phone application in communication with the cloud platform can download and edit the scene service.

[0060] The scene service can be regarded as a service or micro-service deployed and run in a program architecture, and in the embodiments, the scene service can also be referred to as: vehicle running scene; or simply referred to as: scene.

[0061] Further, one or more logic scripts can be included in one scene service; each logic script can be composed of one or more logic episodes; and each logic episode is composed of at least one trigger, at least one condition and at least one action.

[0062] For example, "voice start air conditioner" can be a specific scene, which includes a parent script "voice start" and a child script "start air conditioner".

[0063] Further, taking the parent script as an example, one episode is included, that is, the action of "starting the child script" is executed by monitoring the voice instruction.

[0064] Further, in the episode, the trigger for monitoring the voice instruction, the trigger condition of recognizing the specified voice instruction, and the action of executing "starting the child script" are included.

[0065] Further, when the episode is executed, the trigger will continuously monitor the voice instruction, and when the specified voice instruction of "starting the air conditioner" is recognized, the action of "starting the child script" is executed.

[0066] Each type of trigger can be used to actively and continuously monitor the change of the state of the corresponding type within a period of time, for example, the temperature type trigger can be used to continuously monitor the change of the temperature; other types of triggers can also be used to continuously and passively receive the state of the corresponding type, for example, the voice type trigger can continuously monitor whether the user of the vehicle machine issues a voice instruction, and identify the issued voice instruction.

[0067] Further, conditions can be set in the logical plot, which can also be referred to as trigger conditions in the embodiment, for evaluating the state monitored by the trigger, and when the state monitored by the trigger meets the corresponding trigger condition, the preset action in the logical plot can be triggered.

[0068] It can be seen that each logical plot specifically describes a set of execution logics combined by the triggering mode and the execution mode of the action when the vehicle machine executes one or more actions, and the execution logic in each logical plot is the minimum combination and has atomicity that cannot be divided, and in the embodiment, the logical plot can also be referred to as a plot.

[0069] Further, one plot can serve as a logical script, and multiple plots can form a logical script in a preset order through a series connection, and be used to execute multiple sets of execution logics, and in the embodiment, the logical script can also be referred to as a script.

[0070] Further, one script can be used in multiple scene services, and when more than one script is included in one scene service, the multiple scripts will be connected in the form of parent-child scripts.

[0071] Specifically, the parent script can be regarded as the first-level logical script that is executed first in the same scene service; the child script, as the next-level logical script of the first-level logical script, needs to be started after the execution of the parent script is completed, and is used to undertake the logical actions that need to be executed after the parent script.

[0072] In the embodiment, the scene service can also adopt other ways when deploying the execution logics, for example, directly deploying all the execution logics, instead of deploying the execution logics in the form of scripts and plots through the grouping and series connection of the execution logics.

[0073] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0074] Reference Figure 1 The processing method of the scene service of one embodiment of the present application is applied to a mobile terminal, and specifically includes the following steps:

[0075] Step S101, downloading the general scene service and the user scene service with the category identifier from the cloud platform.

[0076] In the embodiments of the present application, based on the general scene service and the user scene service published by the cloud platform to the mobile terminal, the mobile terminal can download the general scene service marked with the category identifier, and the user scene service without the category identifier.

[0077] The category identifier specifically includes a main category identifier about a main scene and a sub-category identifier about a sub-scene.

[0078] Specifically, each general scene service with the same main category identifier can be regarded as belonging to the same main category.

[0079] Further, each general scene service with the same sub-category identifier can be regarded as belonging to the same sub-category.

[0080] Step S102, adding the category identifier to each user scene service.

[0081] In the embodiments of the present application, for the downloaded user scene service without the category identifier, the user scene service can be marked with a custom category identifier according to the secondary editing of each user scene service.

[0082] The user can mark the user scene service with a custom new category identifier according to the requirement, that is, the category identifier is different from any existing category identifier.

[0083] Further, each user scene service can be marked with an existing main category identifier or sub-category identifier, that is, the user scene service is marked with the category identifier currently used by other general scene services.

[0084] Step S103, classifying the scene services according to the category identifier, and enabling or disabling each scene service according to the category, the scene services including the general scene services and the user scene services.

[0085] In the embodiments of the present application, based on the category identifier marked on the user scene service in the foregoing step, each general scene service can be classified, and the sub-category of the main category can be specifically divided.

[0086] Specifically, after downloading the general scene service, the mobile terminal can divide the general scene services with the same sub-category into the same sub-category according to the category identifier of each general scene service.

[0087] Further, each general scene service with the same main category is divided into the same main category.

[0088] In the embodiment, based on the customized category identification added for the user scenario service, it can be seen that according to the category identification added, it can be separately divided into a category, so as to customize the category division of each user scenario service.

[0089] Further, based on the existing category identification added for each user scenario service, the user scenario service can also be added to the existing category, and the user scenario service and the general scenario service are classified into the same category.

[0090] In a specific example, for example, in the scenario service "fatigue reminder" and the scenario service "distraction reminder", the same main category identification "danger warning" is included, therefore, the scenario service "fatigue reminder" and the scenario service "distraction reminder" belong to the same main category.

[0091] Further, in the scenario service "fatigue reminder", the scenario service "mild fatigue reminder", the scenario service "moderate fatigue reminder", and the scenario service "light and heavy fatigue reminder" are also included, and the above three scenario services have the same subcategory identification "fatigue reminder", therefore, the scenario service "mild fatigue reminder", the scenario service "moderate fatigue reminder", and the scenario service "light and heavy fatigue reminder" belong to the same subcategory. Further, the mobile terminal can start and stop the general scenario service under one category based on the divided main category and subcategory.

[0092] Specifically, when starting any one scenario service in a main category, other scenario services in the main category will be started at the same time.

[0093] Further, when stopping any one scenario service in a main category, other scenario services in the main category will be stopped at the same time.

[0094] Further, when starting any one scenario service in a subcategory, other scenario services in the subcategory will be started at the same time.

[0095] Further, when stopping any one scenario service in a subcategory, other scenario services in the subcategory will be stopped at the same time.

[0096] It can be seen that the processing method of the scene service of the embodiment of the present application is applied to the mobile terminal, based on the general scene service with the category identifier, and comprehensively considers the demand for custom division of the user scene service to perform the category division of all scene services, so that after the general scene service is classified by the category identifier, the user scene service can be individually classified by the user, or can be classified together with the general scene service. After the user scene service is classified into the category of the general scene service, the conflict of the execution logic can be reduced, the user's custom demand and the robustness of the scene service in execution are taken into account, and at the same time, based on the category division of the scene service, the mobile terminal can start and stop all scene services in the same category by selecting a category.

[0097] Reference Figure 2 The processing method of the scene service of an embodiment of the present application is applied to the cloud platform, and specifically includes the following steps:

[0098] Step S201, all scene services are divided into general scene services and user scene services according to different permissions of the execution logic created in each scene service.

[0099] In the embodiment of the present application, based on the architecture characteristics of the deployment execution logic of the scene service, different deployment methods can give different permissions to the user, and based on this, the scene service can be divided into general scene services and user custom services. The user permission is the permission given to the user.

[0100] Specifically, the scene service composed of the above-mentioned script is used as a general scene service in this embodiment, and because the execution logic of the deployment therein is complex, in order to reduce the program conflict during execution, the trigger in the general scene service, the state monitored by the trigger, the condition of evaluating each state, and the action of execution are all set to fixed content, that is, after the cloud platform builds the general scene service, it cannot be changed, and the user does not support secondary editing.

[0101] Further, the scene service can also be constructed without the above-mentioned script and plot, in this embodiment, the scene service can also be constructed by the cloud platform issuing a program template to the mobile terminal, wherein the trigger, condition and action in the program template, as well as the execution logic between them can be directly edited by the user through the mobile terminal, in turn to construct the user scene service, and synchronize it to the cloud. It can be seen that the content executed in the user scene service is edited by the user, and the user can modify it. In this embodiment, the program template can also be referred to as a scene template.

[0102] Based on this, the cloud platform can determine whether the scene service belongs to a general scene service or a user scene service by judging whether the scene service has opened the secondary editing permission to the user.

[0103] As can be seen, based on the architecture of the scene service, the scene service can be classified to distinguish the general scene service with complex execution logic and the user scene service with simple execution logic, and the user's demand is also distinguished from the general demand.

[0104] In step S202, among all the general scene services, the general scene services in which the same logic script is deployed and the same logic script is deployed in the same architecture level are divided into the same category, wherein each logic script is used to deploy at least one complete and indivisible execution logic.

[0105] In the embodiment of the present application, for the general scene service, different logic scripts and different logic plots deployed therein can be used to further subdivide each general scene service into different categories.

[0106] Specifically, the scene services with the same script in each general scene service can be used as the same category of scene service candidates.

[0107] Among them, by judging whether the plots contained in each of them are the same, it can be judged whether the two scripts are the same script.

[0108] Further, to judge whether any two plots are the same, it is necessary to judge whether the trigger deployed in each plot, the state monitored by the trigger, the condition of the state, and the action are the same.

[0109] Further, between any two plots, when the trigger, state, condition and action deployed in each of them are the same, it can be determined that the two plots are the same plot, that is, when two plots are regarded as two groups of execution logic, only when the two groups of execution logic are completely consistent, it can be determined that the two plots are the same.

[0110] Further, between any two scripts, when all the plots contained in each of them are the same and the order of concatenation is consistent, it can be determined that the two scripts are the same script.

[0111] Specifically, when the vehicle functions called by the two scripts control the vehicle at the same time, but one is a parent script and the other is a child script, since the last action executed by the parent script is usually the action of starting to execute the child script, and the last action executed by the child script is usually the action of stopping the script, therefore, to determine that the two scripts are the same, it is necessary that all the plots of each of them, and the trigger, condition and action in each plot are completely consistent.

[0112] Further, for any two generic scene services, if they have at least one same script, it can be considered that both of the generic scene services have performed at least one same execution logic, that is, both of them have triggered the same action based on the same evaluation condition on the same state, and thus, the two generic scene services with at least one same script can be considered as candidate same-type scene services.

[0113] Further, for the two generic scene services with the same script, it is further needed to determine whether the same script is at the same architecture level.

[0114] Specifically, for the two generic scene services with the same script, when the same script is deployed at the first level of the respective generic scene, it can be considered that the script is a parent script that is executed first, that is, at this time, the starting actions triggered by the two generic scene services are the same, and thus, the two generic scene services can be determined to belong to the same category and can be determined to belong to the same main category.

[0115] Further, when the same script is deployed at the last level of the respective generic scene, it can be considered that the script is a child script that is executed last, that is, at this time, the ending actions triggered by the two generic scene services are the same, and thus, the two generic scene services can be determined to belong to the same main category.

[0116] In a specific example, for a generic scene service A: "Voice starts efficient cooling", which includes a parent script: "Voice starts", and a child script: "Efficient cooling" connected in series with the parent script; and another generic scene service B: "Automatic starts efficient cooling", which includes a parent script: "Automatic starts", and a child script: "Efficient cooling" connected in series with the parent script.

[0117] Among them, the child scripts of the two generic scene services are scripts containing 1 plot, and specifically include recognizing a cooling instruction through a car machine system, and performing a preset action: starting a vehicle-mounted air conditioner to cool when the "efficient cooling" instruction is recognized.

[0118] It can be seen that the generic scene service A and the generic scene service B both include the same child script, which is the same function of controlling the vehicle cabin through the same instruction.

[0119] Based on this, the generic scene service A and the generic scene service B can be determined as efficient cooling type scenes.

[0120] Further, for any two generic scene services, if they have at least one same trigger, state, condition, and action, it can be considered that the two generic scene services have at least one related script.

[0121] Further, for two generic scene services with related scripts, it is also needed to determine whether the same scripts in them are at the same architecture level.

[0122] Specifically, for two generic scene services with related scripts, when the related scripts are both deployed at the first level of the respective generic scene, it can be considered that the scripts are both the parent scripts executed first, that is, at this time, the starting actions triggered by the two generic scene services are related, thus the two generic scene services can be determined to belong to the same subcategory, and can be determined to belong to the same subcategory.

[0123] Further, when the related scripts are both deployed at the last level of the respective generic scene, it can be considered that the scripts are both the child scripts executed last, that is, at this time, the ending actions triggered by the two generic scene services are related, thus the two generic scene services can be determined to belong to the same subcategory.

[0124] In a specific example, for the generic scene service C: “Voice to turn on seat ventilation”, there is a parent script: “Voice to turn on”, and a child script: “Seat ventilation” connected in series with the parent script.

[0125] Among them, for the parent script in the generic scene service C, the voice instruction issued by the passenger is recognized through a voice type trigger, and the semantics of “seat ventilation” is taken as a condition, and when the condition is met, a preset action is executed: starting the specified child script “seat ventilation”.

[0126] Further, compared with the parent script in the generic scene service A, the voice instruction issued by the passenger is recognized through a voice type trigger, and the semantics of “efficient cooling” is taken as a condition, and when the condition is met, a preset action is executed: starting the specified child script “efficient cooling”.

[0127] It can be seen that the generic scene service A and the generic scene service C only have the same trigger, but the state monitored by the trigger, the condition of evaluating the state, and the action executed are all different, based on which the generic scene service A and the generic scene service C can be determined as scene services of the voice instruction type.

[0128] Further, in the scene service of the voice instruction type, different child scripts can be connected in series after the child script of the generic scene service A to further refine the classification.

[0129] Further, for the same generic scene service, when it is divided according to different scripts, it can be divided into different categories respectively.

[0130] For example, the generic scene service A can belong to both the voice instruction type and the efficient cooling type of scene service.

[0131] It can be seen that the above-mentioned category division is based on the execution logic of each general scenario service, based on which the general scenario services belonging to the same category are difficult to execute simultaneously, reducing the risk of execution conflict.

[0132] Step S203, adding a category identifier to the general scenario services belonging to the same category, and publishing each general scenario service together with the corresponding category identifier to the mobile terminal.

[0133] In a specific example, based on the above-mentioned general scenario services belonging to the same category, a respective category identifier can be added to each of them.

[0134] Further, the general scenario services belonging to the same category can be annotated with the same category identifier, and for the same general scenario service belonging to multiple categories, the category identifier of each category can be annotated.

[0135] Further, when the cloud platform publishes the general scenario services to the mobile terminal, the category identifier added to each general scenario service can be published together.

[0136] Step S204, publishing the user scenario service to the mobile terminal.

[0137] In an embodiment of the present application, after the cloud platform constructs the scenario template, since the scenario template needs to be edited by the user, the scenario template does not have the attribute of category.

[0138] Based on this, the cloud platform can publish the scenario template as a user scenario service directly to the mobile terminal without adding a category identifier.

[0139] It can be seen that the category of the user scenario service can change according to the secondary editing of the scenario template by the user.

[0140] It can be seen that the scenario service processing method of the embodiments of the present application is applied to the cloud platform, which divides the scenario services into user scenario services and general scenario services based on different permissions of the scenario services, and performs different category division methods respectively. In the category division of the general scenario services, the series relationship of the deployed plots and scripts is comprehensively considered, and the category is divided according to each group execution logic and the deployment level, so that the general scenario services of the same category have the same or related parts in structure and function, and after the category division, the general scenario services of different categories are published to the mobile terminal by marking the category identifier, thereby realizing effective classification of the scenario services, based on the same execution logic, and ensuring that the general scenario services of the same category are difficult to start simultaneously, reducing the conflict between the execution logics.

[0141] The processing method of the scenario service of another embodiment of the present application is applied to a car machine end, and the method comprises the following steps:

[0142] Downloading the scenario service with preset main category identifier and / or subcategory identifier from the cloud platform.

[0143] Dividing the scenario services with the same main category identifier into the same main category, and dividing the scenario services with the same subcategory identifier under the same main category into the same subcategory.

[0144] In response to enabling or disabling any scenario service, other scenario services with the same main category as the scenario service are all adjusted to the same enabled or disabled state.

[0145] In response to enabling or disabling any scenario service, other scenario services with the same subcategory as the scenario service are all adjusted to the same enabled or disabled state.

[0146] It should be noted that the method of the embodiments of the present application can be executed by a single device, such as a computer or a server, etc. The method of the embodiments can also be applied to a distributed scenario and completed by multiple devices in cooperation. In the case of such a distributed scenario, one of the multiple devices can only execute one or more steps in the method of the embodiments of the present application, and the multiple devices can interact with each other to complete the method.

[0147] It should be noted that some embodiments of the present application are described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than the order described above and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0148] Based on the same inventive concept, the embodiments of the present application also provide a scenario service processing device corresponding to any of the above-mentioned embodiment methods.

[0149] Reference Figure 3 The scenario service processing device comprises a scenario service downloading module 301, an identifier adding module 302, and a scenario service classification module 303.

[0150] The scenario service downloading module 301 is configured to download general scenario services and user scenario services with category identifiers from a cloud platform.

[0151] The identifier adding module 302 is configured to add the category identifiers to each user scenario service.

[0152] The scene service classification module 303 is configured to classify scene services according to the category identifiers, and enable or disable each scene service according to the category, wherein the scene services include the general scene services and the user scene services.

[0153] As an optional embodiment, the scene service classification module 303 is specifically configured to:

[0154] The category identifier is configured as a main category identifier and a sub-category identifier;

[0155] Further, the general scene services and the user scene services having the same main category identifier are divided into the same main category;

[0156] The general scene services and the user scene services having the same sub-category identifier in the same main category are divided into the same sub-category.

[0157] Further, in response to enabling or disabling any scene service, other scene services having the same main category as the scene service are all adjusted to the same enabled or disabled state;

[0158] In response to enabling or disabling any scene service, other scene services having the same sub-category as the scene service are all adjusted to the same enabled or disabled state.

[0159] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the embodiments of the present application also provide a scene service processing device.

[0160] Reference Figure 4 The scene service processing device includes a type division module 401, a general scene service classification module 402, a general scene service publishing module 403, and a user scene service publishing module 404.

[0161] The type division module 401 is configured to divide all scene services into general scene services and user scene services according to different permissions of execution logic created in each scene service.

[0162] The general scene service classification module 402 is configured to divide, among all the general scene services, general scene services in which the same logic script is deployed and the same logic script is deployed in the same architecture level into the same category, wherein each logic script is used to deploy at least one complete and indivisible execution logic.

[0163] The general scenario service publishing module 403 is configured to add a category identifier to the general scenario services belonging to the same category, and publish each general scenario service to the mobile terminal together with the corresponding category identifier.

[0164] The user scenario service publishing module 404 is configured to publish the user scenario service to the mobile terminal.

[0165] As an optional embodiment, the type classification module 401 is specifically configured to:

[0166] determine whether the execution logic in each scenario service supports secondary editing;

[0167] in response to the execution logic not supporting secondary editing, determine the scenario service as a general scenario service;

[0168] in response to the execution logic supporting secondary editing, determine the scenario service as a user scenario service.

[0169] For the convenience of description, the above apparatus is described in various modules in terms of functions. Of course, the functions of the modules can be implemented in one or more software and / or hardware in the implementation of the embodiments of the present application.

[0170] The apparatus of the above embodiments is used to implement the processing method of the corresponding scenario service in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be described here.

[0171] Based on the same inventive concept, corresponding to any of the above method embodiments, the embodiments of the present application also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the processing method of the scenario service according to any of the above embodiments when executing the program.

[0172] Figure 5 A more specific hardware structure schematic diagram of an electronic device provided by the present embodiment is shown, which can include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 for communication within the device.

[0173] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits, etc., for executing relevant programs to implement the technical solutions provided by the embodiments of the present application.

[0174] The memory 1020 can be implemented by a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, etc. The memory 1020 can store an operating system and other application programs, and when the technical solutions provided by the embodiments of the present application are implemented by software or firmware, relevant program codes are stored in the memory 1020 and called and executed by the processor 1010.

[0175] The input / output interface 1030 is configured to connect input / output modules to implement information input and output. The input / output modules can be configured as components in the device (not shown in the figure) or externally connected to the device to provide corresponding functions. The input devices can include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices can include a display, a speaker, a vibrator, an indicator light, etc.

[0176] The communication interface 1040 is configured to connect a communication module (not shown in the figure) to implement communication interaction between the device and other devices. The communication module can realize communication through a wired manner (for example, a USB, a network cable, etc.) or through a wireless manner (for example, a mobile network, WIFI, Bluetooth, etc.).

[0177] The bus 1050 includes a channel for transmitting information between various components (for example, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040) of the device.

[0178] It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device can also include other components necessary for normal operation. In addition, those skilled in the art can understand that the above device can also only include components necessary for implementing the solutions of the embodiments of the present application, and does not have to include all the components shown in the figure.

[0179] The device of the above embodiments is used to implement the processing method of the corresponding scenario service in any of the preceding embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described here again.

[0180] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present application also provides a vehicle, comprising a processor and a storage medium, the storage medium is used to store computer instructions, the computer instructions are used to make the processor execute the processing method of the scenario service applied to the vehicle terminal.

[0181] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present application also provides a computer readable storage medium, which stores computer instructions, the computer instructions are used to make the computer execute the processing method of the scenario service as described in any of the above embodiments.

[0182] The computer readable medium of the present embodiment includes permanent and non-permanent, removable and non-removable media, which can be realized by any method or technology to store information. The 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0183] The storage medium of the above embodiments stores computer instructions for making the computer execute the processing method of the scenario service as described in any of the above embodiments, and has the beneficial effects of the corresponding method embodiments, which are not described here again.

[0184] Those skilled in the art should understand that the discussion of any of the above embodiments is only exemplary, and is not intended to imply that the scope (including claims) of the present application is limited to these examples; under the idea of the present application, the above embodiments or technical features in different embodiments can also be combined, the steps can be implemented in any order, and there are many other changes of different aspects of the embodiments of the present application as described above. In order to be brief, they are not provided in detail.

[0185] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application may be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0186] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0187] The embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of this application.

Claims

1. A processing method of a scenario service, characterized by, The method applied to a mobile terminal comprises: Downloading user scenario services and general scenario services with category identifiers from a cloud platform; Adding the category identifiers to each user scenario service; Classifying the scenario services according to the category identifiers, and enabling or disabling each scenario service according to the category, wherein the scenario services include the general scenario services and the user scenario services; The category identifiers include main category identifiers and sub-category identifiers; The classifying the scenario services according to the category identifiers comprises: Dividing the general scenario services and the user scenario services with the same main category identifier into the same main category; Dividing the general scenario services and the user scenario services with the same sub-category identifier in the same main category into the same sub-category; The enabling or disabling each scenario service according to the category comprises: In response to enabling or disabling any scenario service, adjusting all other scenario services in the same main category as the scenario service to the same enabling or disabling state; In response to enabling or disabling any scenario service, adjusting all other scenario services in the same sub-category as the scenario service to the same enabling or disabling state.

2. The method of claim 1, wherein, Each main category is provided with a corresponding main category enabling / disabling button, and each sub-category is provided with a corresponding sub-category enabling / disabling button; The enabling or disabling each scenario service according to the category comprises: In response to clicking any main category enabling / disabling button, adjusting all scenario services in the corresponding main category in the starting state to the disabled state, or adjusting all scenario services in the corresponding main category in the disabled state to the starting state; In response to clicking any sub-category enabling / disabling button, adjusting all scenario services in the corresponding sub-category in the starting state to the disabled state, or adjusting all scenario services in the corresponding sub-category in the disabled state to the starting state.

3. A processing method of a scenario service, characterized by, The method applied to a cloud platform comprises: According to different user permissions of execution logic created in each scenario service, dividing all scenario services into general scenario services and user scenario services; Among all the general scenario services, dividing general scenario services deployed with the same logic script and deployed in the same architecture level into the same category, wherein each logic script is used to deploy at least one complete and indivisible execution logic; Adding category identifiers to the general scenario services belonging to the same category, and publishing each general scenario service together with the corresponding category identifier to a mobile terminal; Publishing the user scenario services to the mobile terminal.

4. The method of claim 3, wherein, According to different user permissions of execution logic created in each scenario service, dividing all scenario services into general scenario services and user scenario services comprises: Determining whether the execution logic in each scenario service is open to secondary editing by a user; In response to the execution logic not supporting secondary editing, determining the scenario service as a general scenario service; In response to the execution logic supporting secondary editing, determining the scenario service as a user scenario service.

5. A processing method of a scenario service, characterized by, The method applied to a vehicle terminal comprises: Downloading scenario services with preset main category identifiers and / or sub-category identifiers from a cloud platform; The scene services with the same main category identifier are classified into the same main category, and the scene services with the same sub-category identifier under the same main category are classified into the same sub-category; In response to enabling or disabling any scene service, other scene services in the same main category as the scene service are all adjusted to the same enabled or disabled state; In response to enabling or disabling any scene service, other scene services in the same sub-category as the scene service are all adjusted to the same enabled or disabled state.

6. A processing apparatus of a scenario service, characterized by, It comprises: a scene service downloading module, an identifier adding module, and a scene service classification module; The scene service downloading module is configured to download general scene services and user scene services with category identifiers from a cloud platform; The identifier adding module is configured to add the category identifiers to each user scene service; The scene service classification module is configured to classify scene services according to the category identifiers and enable or disable each scene service according to the category, wherein the scene services include the general scene services and the user scene services; The scene service classification module is specifically configured to: configure the category identifiers as main category identifiers and sub-category identifiers; classify the general scene services and the user scene services with the same main category identifier into the same main category; classify the general scene services and the user scene services with the same sub-category identifier under the same main category into the same sub-category; In response to enabling or disabling any scene service, other scene services in the same main category as the scene service are all adjusted to the same enabled or disabled state; In response to enabling or disabling any scene service, other scene services in the same sub-category as the scene service are all adjusted to the same enabled or disabled state.

7. A processing apparatus of a scenario service, characterized by, It comprises: a type division module, a general scene service classification module, a general scene service publishing module, and a user scene service publishing module; The type division module is configured to divide all scene services into general scene services and user scene services according to different permissions of execution logic created in each scene service; The general scene service classification module is configured to divide, among all the general scene services, general scene services in which the same logic script is deployed and the same logic script is deployed in the same architecture level into the same category, wherein each logic script is used to deploy at least one complete and indivisible execution logic; The general scene service publishing module is configured to add category identifiers to general scene services belonging to the same category and publish each general scene service together with the corresponding category identifier to a mobile terminal; The user scene service publishing module is configured to publish the user scene services to a mobile terminal.

8. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable by the processor, wherein, The processor executes the computer program to implement the method of any one of claims 1 to 2, or the method of any one of claims 3 and 4, or the method of claim 5.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing a computer to perform the method according to any one of claims 1 to 2, or the method of any one of claims 3 and 4, or the method as claimed in claim 5.

10. A vehicle characterized by comprising: A computer program product comprising a processor and a storage medium storing computer instructions for causing the processor to perform the method according to claim 5.

Images