Data processing method and related device

Abstract

A data processing method and a related device can be applied to the field of language processing. The method comprises the steps of obtaining a first description text of a first description language, wherein the first description text represents a first element of the intelligent terminal in a first scene; a second description text of a second description language is obtained, the second description text represents the first element, and the description name and the parameter type of the first element represented by the first description text are the same as the description name and the parameter type of the first element represented by the second description text; and executing the first description text and the second description text. Through the embodiment of the invention, the description name and the parameter type of the same element can be same by using different description languages, so that the uniformity of the description languages related to automatic driving can be improved, and the development efficiency can be improved.

Description

Data processing method and related device Technical Field

[0001] The present application relates to the field of language processing, and in particular to data processing methods and related devices. Background Art

[0002] With the development of society, more and more machines in modern life are becoming automated and intelligent, and automobiles for mobility are no exception. Vehicles with intelligent driving capabilities (hereinafter referred to as smart vehicles / smart cars) are gradually becoming part of people's daily lives. In recent years, advanced driving assistance systems (ADAS) have played a crucial role in smart cars. They utilize a variety of onboard sensors to monitor the surrounding environment, detect and identify objects, and systematically calculate and analyze the driving environment using data such as maps. This allows for route planning and driving maneuvers, as well as foreseeing potential dangers, effectively enhancing driving comfort and safety.

[0003] Smart driving terminals equipped with intelligent driving systems must pass multiple tests before entering the market. Currently, the relevant description languages ​​used for these tests mainly include the operational design domain (ODD) description language, static scenario description language, dynamic scenario description language, and verification and evaluation description language. Each description language is independent and incompatible, resulting in low design and development efficiency.

[0004] Summary of the Invention

[0005] The embodiments of the present application provide a data processing method and related devices, which can improve the uniformity of description languages ​​related to autonomous driving and help improve development efficiency.

[0006] In a first aspect, an embodiment of the present application provides a data processing method, comprising:

[0007] Acquire a first description text in a first description language, where the first description text represents a first element of the smart terminal in a first scenario;

[0008] Obtaining a second description text in a second description language, where the second description text represents the first element, and the description name and parameter type of the first element represented by the first description text are the same as the description name and parameter type of the first element represented by the second description text;

[0009] The first description text and the second description text are executed.

[0010] In an embodiment of the present application, the description name and parameter type of the same element described using different description languages ​​are the same, which can enhance the uniformity of the description languages ​​related to autonomous driving and help improve development efficiency.

[0011] In a possible implementation, the first element belongs to a predefined first element library;

[0012] The obtaining of the first description text in the first description language includes:

[0013] The first description text is acquired according to the first scene and the first element library.

[0014] In this implementation, the first element library is an element library corresponding to the first description language, that is, the elements in the first element library are elements described in the first description language. Based on the first scenario and the first element library, a first description text corresponding to the first element in the first scenario can be selected from the first element library.

[0015] In a possible implementation, the first element belongs to a predefined second element library;

[0016] The obtaining of the second description text in the second description language includes:

[0017] The second description text is acquired according to the first scene and the second element library.

[0018] In this implementation, the second element library is an element library corresponding to the second description language, that is, the elements in the second element library are elements described in the second description language. According to the first scenario and in combination with the first element library, a first description text corresponding to the first element in the first scenario can be selected from the first element library.

[0019] In a possible implementation, the description name, parameter type, and parameter value of the first element represented by the first description text are the same as the description name, parameter type, and parameter value of the first element represented by the second description text.

[0020] In this implementation, different description languages ​​may have the same description name and parameter type for the same element, and the same parameter values.

[0021] In a possible implementation, the first description language is different from the second description language, and the first description language or the second description language includes:

[0022] Design operation scope ODD description language, static scenario description language, dynamic scenario description language, or verification and evaluation description language.

[0023] In this implementation, the first description language or the second description language can be any one of an ODD description language, a static scene description language, a dynamic scene description language, or a verification and evaluation description language, and the first description language is different from the second description language.

[0024] In a possible implementation, the ODD description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements; or

[0025] The static scene description language describes one or more of the following types of elements: road elements; or

[0026] The dynamic scene description language describes one or more of the following types of elements: environment elements, vehicle status elements; or

[0027] The verification and evaluation description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements.

[0028] In a possible implementation manner, the first element includes one or more elements.

[0029] In a possible implementation, the first element includes multiple elements, and the multiple elements are connected by conjunctions, and the conjunctions include logical conjunctions and / or temporal conjunctions.

[0030] In this implementation method, when the first element includes multiple elements connected by conjunctions, different description languages ​​not only need to have the same description of the same element, but also need to ensure that the conjunctions used are the same, that is, the combination method of the elements is the same, which further improves the uniformity of the description language related to autonomous driving.

[0031] In one possible implementation, the logical connectives include one or more of the following:

[0032] Negation, conjunction, disjunction, deduction, equivalence.

[0033] In a possible implementation, the temporal connectives include one or more of the following:

[0034] Until, always, eventually.

[0035] In a second aspect, an embodiment of the present application provides a data processing device, including:

[0036] An acquiring unit, configured to acquire a first description text in a first description language, where the first description text represents a first element of the smart terminal in a first scene;

[0037] The acquiring unit is configured to acquire a second description text in a second description language, where the second description text represents the first element, and the description name and parameter type of the first element represented by the first description text are the same as the description name and parameter type of the first element represented by the second description text;

[0038] A processing unit is configured to execute the first description text and the second description text.

[0039] In a possible implementation, the first element belongs to a predefined first element library;

[0040] When acquiring the first description text in the first description language, the acquiring unit is configured to:

[0041] The first description text is acquired according to the first scene and the first element library.

[0042] In a possible implementation, the first element belongs to a predefined second element library;

[0043] When acquiring the second description text in the second description language, the acquiring unit is configured to:

[0044] The second description text is acquired according to the first scene and the second element library.

[0045] In a possible implementation, the description name, parameter type, and parameter value of the first element represented by the first description text are the same as the description name, parameter type, and parameter value of the first element represented by the second description text.

[0046] In a possible implementation, the first description language is different from the second description language, and the first description language or the second description language includes:

[0047] Design operation scope ODD description language, static scenario description language, dynamic scenario description language, or verification and evaluation description language.

[0048] In a possible implementation, the ODD description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements; or

[0049] The static scene description language describes one or more of the following types of elements: road elements; or

[0050] The dynamic scene description language describes one or more of the following types of elements: environment elements, vehicle status elements; or

[0051] The verification and evaluation description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements.

[0052] In a possible implementation manner, the first element includes one or more elements.

[0053] In a possible implementation, the first element includes multiple elements, and the multiple elements are connected by conjunctions, and the conjunctions include logical conjunctions and / or temporal conjunctions.

[0054] In one possible implementation, the logical connectives include one or more of the following:

[0055] Negation, conjunction, disjunction, deduction, equivalence.

[0056] In a possible implementation, the temporal connectives include one or more of the following:

[0057] Until, always, eventually.

[0058] In a third aspect, an embodiment of the present application provides a data processing device, which includes a processor and a memory; a computer program is stored in the memory; when the processor executes the computer program, the computing device executes any method described in the first aspect above.

[0059] It should be noted that the processor included in the data processing device described in the third aspect above may be a processor specifically used to execute these methods (referred to as a dedicated processor for ease of distinction), or may be a processor that executes these methods by calling a computer program, such as a general-purpose processor. Optionally, the at least one processor may include both a dedicated processor and a general-purpose processor.

[0060] Optionally, the computer program may be stored in a memory. For example, the memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same device or provided on separate devices. The embodiments of the present application do not limit the type of memory or the configuration of the memory and the processor.

[0061] In a possible implementation, the at least one memory is located outside the data processing device.

[0062] In another possible implementation, the at least one memory is located within the data processing device.

[0063] In this application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0064] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on at least one processor, the method described in any one of the first aspects is implemented.

[0065] In a fifth aspect, the present application provides a computer program product, which includes computer instructions. When the instructions are executed on at least one processor, the method described in any one of the first aspects is implemented.

[0066] Optionally, the computer program product may be a software installation package. When the aforementioned method is required, the computer program product may be downloaded and executed on a computing device.

[0067] The beneficial effects of the technical solutions provided in the second to fifth aspects of this application can refer to the beneficial effects of the technical solution in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] FIG1 is a schematic diagram of a possible data processing method provided in an embodiment of the present application;

[0069] FIG2 is a schematic diagram of a scenario provided by an embodiment of the present application;

[0070] FIG3 is a schematic structural diagram of a data processing device 30 provided in an embodiment of the present application;

[0071] FIG4 is a schematic structural diagram of another possible data processing device 40 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0072] The embodiments of the present invention will be described below with reference to the accompanying drawings.

[0073] The terms "first," "second," "third," and "fourth," etc., in the specification and claims of this application and the accompanying drawings are used to distinguish between different objects, rather than to describe a specific order. In addition, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0074] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0075] As used in this specification, the terms "component," "module," "system," and the like are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0076] To facilitate understanding of the relevant contents of the embodiments of this application, some of the knowledge required for the solution of this application is introduced below. It should be noted that these explanations are intended to make the embodiments of this application easier to understand and should not be regarded as limiting the scope of protection claimed by this application.

[0077] 1. Operational design domain (ODD)

[0078] ODD, also known as the design operating range or operational design conditions (ODC), refers to the operating conditions under which an autonomous driving system or feature is designed to operate. In layman's terms, these are the operating conditions for a particular autonomous driving function. Examples of these conditions include, but are not limited to, the environment, geographic location, time constraints, traffic and road characteristics, vehicle status, and driver status.

[0079] 2. Smart terminals

[0080] The smart terminal in the embodiments of the present application is a device with behavioral capabilities. For example, the smart terminal can be a device that can be driven by power to move, such as a vehicle, drone, wheeled mobile robot or other transportation device or vehicle.

[0081] 3. Logical operators

[0082] Logical operators, also known as logical connectives, logical conjunctions, or logical operators, can connect multiple elements. See Table 1. Logical operators include but are not limited to the operators shown in Table 1.

[0083] Table 1

[0084] 4. Timing Operators

[0085] Temporal operators are also called temporal connectives, temporal conjunctions, or temporal operators. Temporal operators are used to represent events in time. Possible examples of temporal operators include, but are not limited to, those shown in Table 2.

[0086] Table 2

[0087] 5. Natural language description text

[0088] Natural language description text refers to text in natural language form, and the text here includes but is not limited to character strings, formulas, paragraphs, or complete documents.

[0089] 6. Proposition

[0090] A proposition is the semantic meaning of a declarative sentence and can be judged as true or false. For example, vehicle A's current speed meets the speed limit. For the proposition "Vehicle A's current speed is greater than the maximum speed limit," its truth value is false. For the proposition "Vehicle A's current speed is less than the maximum speed limit," its truth value is true.

[0091] Propositions can include atomic propositions and compound propositions. Atomic propositions are propositions that cannot be divided any further. Compound propositions are propositions formed by connecting atomic propositions with connectives.

[0092] The above exemplary description of the concepts can be applied hereinafter.

[0093] Currently, the main description languages ​​used for testing include the operational design domain (ODD) description language, static scenario description language, dynamic scenario description language, and verification and evaluation description language. Each description language is independent and incompatible, resulting in low design and development efficiency.

[0094] Based on this, the embodiments of the present application provide a description language, a data processing method and related devices, which are designed to use the same description name and parameter type for the same element described in different description languages, thereby improving the uniformity of the description language related to autonomous driving. For developers, it is easier to understand the relevant description text, which is conducive to improving development efficiency.

[0095] The following first introduces the element library of the description language in this application.

[0096] An embodiment of the present application provides a language for describing elements in an element library. When the language is used to describe elements in different element libraries, the same element in different element libraries can be represented using the same description name and parameter type.

[0097] Exemplarily, the language can be used to describe elements in the ODD element library. For example, taking the description of the "environment" element as an example, a language text can be in the form of environment(parameter 1, parameter 2), where the description name is environment, the parameter type is defined by parameter 1, and the parameter value is defined by parameter 2. For example, parameter 1 can be 'weather', or 'envIlluminance', etc., which respectively represent the weather environment, or the lighting environment, etc. When parameter 1 is 'weather', it represents the weather environment. At this time, the value of parameter 2 can be 'clear', 'fog', 'rain', or 'snow', etc., which respectively represent clear weather, foggy weather, rainy weather, or snowy weather, etc.

[0098] Optionally, also taking the description of the "environment" element as an example, another understanding of environment(parameter 1, parameter 2) is: environment represents the description name, parameter 1 and parameter 2 both represent parameter types, where the parameter type is an enumeration type, where the parameter value is an enumeration value. For example, the type of parameter 1 is an enumeration type, which represents the environment type. The enumeration values ​​include 'weather', or 'envIlluminance', etc., which respectively represent the weather environment, or the lighting environment, etc. The type of parameter 2 is an enumeration type, which represents the specific category of parameter 1. When parameter 1 is 'weather', it represents the weather environment. At this time, the enumeration value of parameter 2 can be 'clear', 'fog', 'rain', or 'snow', etc., which respectively represent clear weather, foggy weather, rainy weather, or snowy weather, etc.

[0099] For example, to describe the "road" element, a language text might look like road('parameter 1', 'parameter 2'), where the description name is road, the parameter type is defined by parameter 1, and the parameter value is defined by parameter 2. For example, parameter 1 could be 'roadType', 'laneId', 'laneNum', or 'laneType', representing the road type, road sign, number of lanes, or lane type, respectively. If parameter 1 is 'roadType', indicating the road type, parameter 2 could be 'highway' or 'expressway', representing a highway or expressway, respectively.

[0100] Optionally, the description name and parameter type of the road element in the ODD description language can be the same as those in the dynamic scenario description language and the verification and evaluation description language. The description name and parameter type of the environment element and vehicle status element in the ODD description language can be the same as those in the static scenario description language and the verification and evaluation description language. In other words, the description name and parameter type of the same element in different description languages ​​can be the same, and optionally, the parameter values ​​can also be the same.

[0101] The data processing method and related devices provided by this application will be described in detail below with reference to the accompanying drawings. It should be noted that the business scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided by this application. It should be understood that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided by this application are also applicable to similar technical problems.

[0102] Please refer to Figure 1, which is a schematic diagram of a possible data processing method provided by an embodiment of the present application. As shown in Figure 1, the data processing method includes the following steps S101 to S103. The execution subject of the method shown in Figure 1 can be any electronic device or platform with data processing capabilities, for example, it can be a server, a computer device, a cloud platform, a chip in an electronic device, etc., which is not limited here. Figure 1 mainly illustrates an electronic device as the execution subject of the method. It should be noted that Figure 1 is a schematic flow chart of an embodiment of the method of the present application, showing the detailed communication steps or operations of the method, but these steps or operations are only examples. The embodiment of the present application can also perform other operations or variations of the various operations in Figure 1. In addition, the various steps in Figure 1 can be executed in a different order from that presented in Figure 1, and it may not be necessary to execute all the operations in Figure 1. Among them:

[0103] S101: The electronic device obtains a first description text in a first description language.

[0104] In some feasible implementations, the first description text represents the first element of the smart terminal in the first scenario. Here, the first scenario can be understood as a scenario during a smart terminal simulation test described using multiple elements. For example, the first scenario can include a description of the environment, where the environment can include weather, lighting, or geographic conditions. For another example, the first scenario can also include a description of the vehicle's status, such as vehicle speed, etc., without limitation.

[0105] Wherein, the first element belongs to a predefined first element library. It should be understood that the elements included in the first element library are elements described in a first description language. Wherein, the first description language can be any one of an ODD description language, a static scene description language, a dynamic scene description language, or a verification and evaluation description language. It should be noted that the various elements in the first element library can be presented in the form of a table, a set or a matrix, and this application does not impose any restrictions on this. Optionally, the first element library may include all elements that can be described in the first description language, or the first element library may also include some elements that can be described in the first description language, which is not restricted here.

[0106] Exemplarily, the above-mentioned obtaining the first description text in the first description language can be understood as: obtaining the first description text based on the first scenario and the first element library. Exemplarily, the first description text can be a string or code, etc., which is not limited here. Optionally, the above-mentioned obtaining the first description text in the first description language can also be understood as receiving the first description text in the first description language.

[0107] It should be understood that the elements included in the first element library of the embodiment of the present application can be one or more of road-related elements, environment-related elements, vehicle status-related elements, etc., without limitation herein. For example, assuming that the first element library is an element library corresponding to the ODD description language (i.e., the ODD element library), then the first element library can include one or more of road-related elements, environment-related elements, or vehicle status-related elements, etc. For another example, assuming that the first element library is an element library corresponding to the static scene description language (i.e., the static scene element library), then the first element library can include road-related elements. For another example, assuming that the first element library is an element library corresponding to the dynamic scene description language (i.e., the dynamic scene element library), then the first element library can include one or more of environment-related elements, or vehicle status-related elements, etc. For another example, assuming that the first element library is an element library corresponding to the verification and evaluation description language (i.e., the verification and evaluation element library), then the first element library can include one or more of road-related elements, environment-related elements, or vehicle status-related elements, etc.

[0108] For example, road-related elements may include road type (roadType), road identifier (laneId), lane number (laneNum), lane type (laneType), etc. For example, road types may include urban roads, highways, factory roads, forest roads, and rural roads. Urban roads are further divided into four categories: expressways, arterial roads, collector roads, and access roads. Highways are further divided into five categories: expressways, first-class highways, second-class highways, third-class highways, and fourth-class highways. Lane types may include driving lanes, emergency lanes, and bus lanes. Environmental elements may include, for example, weather conditions (weather), illumination conditions (envIlluminance), and temperature conditions (temperature). For example, weather conditions may include clear, foggy, rainy, or snowy, and illumination conditions may include low or high illumination. Vehicle status elements may include, for example, vehicle speed (speed), time distance to the vehicle in front (time distance), and autonomous driving function. For example, vehicle speed may include the speed of the own vehicle (ego) and the speed of the vehicle in front (fo), and autonomous driving function may include lane keeping (keepLane), etc. This application does not impose any restrictions on this.

[0109] S102: The electronic device obtains a second description text in a second description language.

[0110] In some feasible implementations, the second description text represents the first element, wherein the first element belongs to a predefined second element library. It should be understood that the elements included in the second element library are elements described in a second description language. Wherein, the second description language can be any one of an ODD description language, a static scene description language, a dynamic scene description language, or a verification and evaluation description language, and the second description language is different from the first description language. It should be noted that each element in the second element library can be presented in the form of a table, a set, etc., and this application does not limit this. Optionally, the second element library can include all elements in the elements that can be described in the first description language, or the second element library can also include some elements in the elements that can be described in the first description language, which is not limited here.

[0111] Exemplarily, the above-mentioned acquisition of the first description text in the second description language can be understood as: acquiring the second description text based on the first scene and the second element library. It should be understood that the elements included in the second element library in the present application can also be one or more of road-related elements, environmental elements, vehicle status elements, etc., which are not limited here. Among them, the understanding of various types of elements can be referred to the relevant description in step S101, which will not be repeated here. Optionally, the above-mentioned acquisition of the first description text in the second description language can also be understood as: receiving the first description text in the second description language.

[0112] It should be noted that the description name and parameter type of the first element of the first description text representation in this application are the same as the description name and parameter type of the first element of the second description text representation. Optionally, the description name, parameter type and parameter value of the first element of the first description text representation are the same as the description name, parameter type and parameter value of the first element of the second description text representation. For example, the ODD description language, dynamic scene description language and verification evaluation description language all have descriptions of the environment. For example, the descriptions of the three all use environment() to represent the environment. Environment() can have two parameters, recorded as environment(parameter 1, parameter 2). When parameter 1 is 'weather', it represents the weather environment. At this time, the value of parameter 2 can be 'clear', 'fog', 'rain', 'snow', etc., which respectively represent clear weather, foggy weather, rainy weather, snowy weather, etc. The environment('weather','clear') in the ODD element library indicates that the ODD of the autonomous driving vehicle is sunny. The environment('weather','clear') in the dynamic scene element library indicates that the weather in the test scene is sunny. The environment('weather','clear') in the verification and evaluation element library indicates whether the weather is sunny.

[0113] For example, taking the first scenario shown in Figure 2 as an example, assume that the natural language description text of the first scenario is "The autonomous driving vehicle is operating in clear weather, the road type is highway, the road sign is 4213, the number of lanes is 6, including 4 driving lanes and 2 emergency lanes, the speed range is [0, 60] km / h, the autonomous driving function is lane keeping, the speed range of the vehicle in front of the autonomous driving vehicle is [0, 60] km / h, the time distance between the autonomous driving vehicle and the vehicle in front is 4s, and the behavior of the vehicle in the front is lane keeping."

[0114] In one implementation, if the first scenario described above is described using the ODD description language, the elements in the ODD element library can be described as shown in Table 3 below, and can include one or more elements of the environment class, road class, or vehicle status class. Among them, environment('weather','clear') indicates that the weather condition in the autonomous vehicle's ODD is clear weather, road('roadType','highway') indicates that the road type in the autonomous vehicle's ODD is a highway, speed(ego,'belong_to',[0,60]) indicates that the vehicle speed in the autonomous vehicle's ODD is 0-60 km / h, and keepLane(ego) indicates that the autonomous driving function in the autonomous vehicle's ODD is lane keeping.

[0115] Table 3

[0116] Optionally, if the first scenario described above is described using a static scenario description language, the elements in the static scenario element library can be described as shown in Table 4 below, specifically including road-related elements. Here, road('roadType','highway') indicates that the test scenario for the autonomous vehicle is a highway, road('laneId',4213) indicates that the road ID of the test scenario is 4213, road('laneNum',6) indicates that the number of lanes in the test scenario is 6, and lane('laneType',['driving',4,'emergency',2]) indicates that the test scenario includes 4 driving lanes and 2 emergency lanes. The description of road('roadType','highway') in the static scenario description language is consistent with the description of the road type in the ODD description language, including the same element description name, parameter type, and parameter value.

[0117] Table 4

[0118] Optionally, if the first scenario is described using a dynamic scenario description language, the elements in the dynamic scenario element library can be described as shown in Table 5 below, specifically including environment and vehicle state elements. Here, environment('weather','clear') indicates that the test scenario is clear weather, speed(ego,'belong_to',[0,60]) indicates that the speed of the autonomous driving vehicle in the test scenario is 0-60 km / h, speed(fo,'belong_to',[0,60]) indicates that the speed of the vehicle in front of the autonomous driving vehicle in the test scenario is 0-60 km / h, distance(ego,fo,'thw','equal_to',4) indicates that the time distance between the autonomous driving vehicle and the vehicle in front of the vehicle in the test scenario is 4 seconds, keepLane(ego) indicates that the behavior of the autonomous driving vehicle in the test scenario is lane keeping, and keepLane(fo) indicates that the behavior of the vehicle in front of the vehicle in the test scenario is lane keeping. The environment('weather','clear'), speed(ego,'belong_to',[0,60]), and keepLane(ego) in the dynamic scene description language are consistent with the descriptions of the environment type, the speed of the autonomous driving vehicle, and the autonomous driving function of the autonomous driving vehicle in the ODD description language, including the same element description names, parameter types, and parameter values.

[0119] Table 5

[0120] Optionally, if the first scenario is described using a verification and evaluation description language, the elements in the verification and evaluation element library can be described as shown in Table 6 below. In the verification and evaluation description language, "follow(ego,fo)" indicates that the autonomous driving vehicle follows the vehicle in the environment ahead, and "collision(ego,fo)" indicates that the autonomous driving vehicle collides with the vehicle in the environment ahead. Indicates that when the autonomous vehicle is in lane keeping mode and following a vehicle ahead, it must not collide with the vehicle ahead. As shown in Table 6, keepLane(ego) is consistent with the lane keeping descriptions for autonomous vehicles in the ODD description language and the dynamic scene description language, including the same element description names, parameter types, and parameter values. road('roadType','highway')&environment('weather','clear')&speed(ego,'belong_to',[0,60])→distance(ego,fo,'thw',greater_than',4) indicates that when the autonomous vehicle is on a highway, in clear weather, and at a speed between 0 and 60 km / h, it must maintain a distance of at least 4 seconds from the vehicle ahead. Similarly, the road('roadType','highway'), environment('weather','clear'), and speed(ego,'belong_to',[0,60]) in the Verification Evaluation Description Language are consistent with the descriptions of road type, environment type, and autonomous vehicle speed in the ODD Description Language, including the same descriptions of element names, parameter types, and parameter values. Optionally, the road('roadType','highway') in the Verification Evaluation Description Language is also consistent with the description of road type in the Static Scene Description Language, and the environment('weather','clear') and speed(ego,'belong_to',[0,60]) in the Dynamic Scene Description Language are also consistent with the descriptions of environment type and autonomous vehicle speed in the Dynamic Scene Description Language.

[0121] It's important to note that elements in the verification and evaluation description language can also have propositional attributes, meaning they can output "True" or "False." For example, if the element in the verification and evaluation library is road('roadType', 'highway'), the output is "True" if the autonomous vehicle is currently on a highway, and "False" if it's not. This allows us to determine whether the autonomous vehicle complies with the verification and evaluation rules.

[0122] Table 6

[0123] It should be understood that the first element can be a single element. For example, in the ODD description language, environment('weather', 'clear') can indicate that the weather condition of the autonomous vehicle's ODD constraint is clear weather, which is a single element description. For another example, road('roadType', 'highway') can indicate that the road condition of the autonomous vehicle's ODD constraint is a highway, which is also a single element description.

[0124] Optionally, the first element may be a plurality of elements. When the first element is a plurality of elements, the plurality of elements may be connected by conjunctions, where the conjunctions may include logical conjunctions and / or temporal conjunctions. For example, It consists of multiple elements and conjunctions, indicating that the ODD weather condition for the autonomous vehicle is sunny and the lighting condition cannot be low light. G means that sunny weather and low light conditions must always be met.

[0125] For example, assume that the natural language description text of the first scenario is "The autonomous driving vehicle is operating in clear weather and the lighting conditions cannot be low light. The road type is a highway or expressway. The road sign is 4213. The number of lanes is 6, including 4 driving lanes and 2 emergency lanes. The speed range of the autonomous driving vehicle is [0, 60] km / h. The speed range of the environmental vehicles in front of the autonomous driving vehicle is [0, 60] km / h. The time distance between the autonomous driving vehicle and the environmental vehicles in front is 4s. When the autonomous driving vehicle is in the same lane and there are environmental vehicles in front, the vehicle can activate the lane keeping function."

[0126] In one implementation, if the first scenario is described using the ODD description language, the elements in the ODD element library can be described as shown in Table 7 below, which may include elements such as environment, road, and vehicle status. Indicates that the weather condition of the autonomous vehicle's ODD is always sunny, and the lighting condition cannot be low light. road('roadType','highway')∨road('roadType','expressway') indicates that the road type in the autonomous vehicle's ODD is a highway or expressway. speed(ego,'belong_to',[0,60]) indicates that the speed in the autonomous vehicle's ODD is 0-60 km / h. position(fo,ego,'lane-sameLane')∧position(fo,ego,'direction-front')→keepLane(ego) indicates that the autonomous vehicle's ODD is that the lane keeping function can only be enabled when the autonomous vehicle is in the same lane and there is an environment vehicle in front.

[0127] Table 7

[0128] Optionally, if the first scenario described above is described using a static scenario description language, the elements in the static scenario element library can be described as shown in Table 8 below, specifically including road-type elements. Here, road('roadType','highway')∨road('roadType','expressway') indicates that the test scenario for the autonomous vehicle is a highway or expressway, road('laneId',4213) indicates that the road ID of the test scenario is 4213, road('laneNum',6) indicates that the number of lanes in the test scenario is 6, and lane('laneType',['driving',4,'emergency',2]) indicates that the test scenario includes 4 driving lanes and 2 emergency lanes. The description of road('roadType','highway')∨road('roadType','expressway') in the static scenario description language is consistent with the description of road types in the ODD description language, including the same element description names, parameter types, parameter values, and the same element combination method (or connection method).

[0129] Table 8

[0130] Optionally, if the first scene is described using a dynamic scene description language, the elements in the dynamic scene element library can be described as shown in Table 9 below, specifically including environment and vehicle status elements. Indicates that the weather conditions of the test scene are always sunny and the lighting conditions cannot be low light. speed(ego,'belong_to',[0,60]) indicates that the speed of the autonomous driving vehicle in the test scene is 0-60km / h. speed(fo,'belong_to',[0,60]) indicates that the speed of the vehicle in front of the autonomous driving vehicle in the test scene is 0-60km / h. distance(ego,fo,'thw','equal_to',4) indicates that the time distance between the autonomous driving vehicle and the vehicle in front of the autonomous driving vehicle in the test scene is 4s. position(fo,ego,'lane-sameLane')∧position(fo,ego,'direction-front') indicates that the autonomous driving vehicle is in the same lane and there is an environmental vehicle in front of it. keepLane(ego) indicates that the autonomous driving vehicle is in lane keeping mode. keepLane(fo) indicates that the vehicle in front of the autonomous driving vehicle is in lane keeping mode. ) and the vehicle's position in the environment (i.e., position(fo,ego,'lane-sameLane') ∧position(fo,ego,'direction-front')) are consistent with the description of the environment type and vehicle's position in the ODD description language, including the same element description names, parameter types, and parameter values, as well as the same element combination (or connection method). Optionally, the description of the autonomous vehicle's speed and autonomous driving function in the dynamic scene description language is consistent with the description of the autonomous vehicle's speed and autonomous driving function in the ODD description language.

[0131] Table 9

[0132] Optionally, if the first scenario is described using a verification evaluation description language, the elements in the verification evaluation element library may be described as shown in Table 10. In the verification evaluation description language, ads('allowed2start') indicates that the autonomous driving system (ADS) is allowed to be activated. Indicates that ADS must be activated when the road type is a highway or expressway, the weather conditions are clear, and the lighting conditions are not low. The expression road('roadType','highway')∨road('roadType','expressway') is identical to the road description statements in the ODD description language and the static scene description language, including the same language elements and the same combination method. The description statements of the environment are the same as those in the ODD description language and the dynamic scene description language, including the same language elements and the same combination method.

[0133] For example, ads('stateOpen') indicates that the ADS is currently active, and ads('request2takeOver') indicates that the ADS requests to take over. [0,10] Indicates that it will happen within the next 10 seconds. This indicates that ADS is currently active, the current road is a highway, and the autonomous vehicle will not be on the highway within the next 10 seconds. Therefore, ADS must request takeover. The road ('roadType', 'highway') is consistent with the road description in the ODD and static scene description languages.

[0134] Table 10

[0135] S103: The electronic device executes the first description text and the second description text.

[0136] Optionally, the electronic device executes the first description text and the second description text to implement testing of the smart terminal in the first scenario. It should be noted that regardless of the form of the first description text and the second description text, such as source code or intermediate documents, testing of the smart terminal implemented using the first description text and the second description text can be understood as executing the first description text and the second description text.

[0137] In an embodiment of the present application, the description name and parameter type of the same element described using different description languages ​​are the same, which can improve the uniformity of the description language related to autonomous driving. For developers, it is easier to understand the relevant description text, which is conducive to improving development efficiency.

[0138] The above describes in detail the method of the embodiment of the present application. The following provides an apparatus of the embodiment of the present application.

[0139] It is understandable that the multiple devices provided in the embodiments of the present application, such as data processing devices, include hardware structures, software units, or combinations of hardware structures and software structures that perform the corresponding functions in order to implement the functions in the above-mentioned method embodiments. Those skilled in the art should easily appreciate that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different device implementations to implement the aforementioned method embodiments in different usage scenarios, and the different implementations of the devices should not be considered to exceed the scope of the embodiments of the present application.

[0140] The embodiments of the present application can divide a device (such as a data processing device) into functional units. For example, each functional unit can be divided according to each function, or two or more functions can be integrated into one functional unit. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0141] Please refer to Figure 3, which is a schematic diagram of the structure of a data processing device 30 provided in an embodiment of the present application. Optionally, the data processing device 30 can be a standalone device or a component included in a standalone device, such as a chip, software module, or integrated circuit. The data processing device 30 is used to implement the aforementioned control method, for example, the method used to implement the electronic device in the embodiment described in Figure 1.

[0142] In one possible implementation, the data processing device 30 may include an acquisition unit 301 and a processing unit 302. The acquisition unit 301 may be used to implement the aforementioned functions of acquiring, receiving, or generating the first description text and the second description text, such as S101 or S102, and / or to support other processes of the technology described in the aforementioned method. In some possible implementation scenarios, the acquisition unit 301 may also be replaced by a communication interface module and / or a transceiver module, and the interface module and / or the transceiver module may be used to support other processes of the technology described in the aforementioned method.

[0143] The processing unit 302 may be configured to execute the aforementioned operations of executing the first description text and the second description text, such as S103 , and / or other processes for supporting the technology described herein.

[0144] In one possible design, the acquiring unit 301 is configured to acquire a first description text in a first description language, where the first description text represents a first element of the smart terminal in a first scenario;

[0145] The acquiring unit 301 is configured to acquire a second description text in a second description language, where the second description text represents the first element, and the description name and parameter type of the first element represented by the first description text are the same as the description name and parameter type of the first element represented by the second description text;

[0146] The processing unit 302 is configured to execute the first description text and the second description text.

[0147] In a possible implementation, the first element belongs to a predefined first element library;

[0148] When acquiring the first description text in the first description language, the acquiring unit 301 is configured to:

[0149] The first description text is acquired according to the first scene and the first element library.

[0150] In a possible implementation, the first element belongs to a predefined second element library;

[0151] When acquiring the second description text in the second description language, the acquiring unit 301 is configured to:

[0152] The second description text is acquired according to the first scene and the second element library.

[0153] In a possible implementation, the description name, parameter type, and parameter value of the first element represented by the first description text are the same as the description name, parameter type, and parameter value of the first element represented by the second description text.

[0154] In a possible implementation, the first description language is different from the second description language, and the first description language or the second description language includes:

[0155] Design operation scope ODD description language, static scenario description language, dynamic scenario description language, or verification and evaluation description language.

[0156] In a possible implementation, the ODD description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements; or

[0157] The static scene description language describes one or more of the following types of elements: road elements; or

[0158] The dynamic scene description language describes one or more of the following types of elements: environment elements, vehicle status elements; or

[0159] The verification and evaluation description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements.

[0160] In a possible implementation manner, the first element includes one or more elements.

[0161] In a possible implementation, the first element includes multiple elements, and the multiple elements are connected by conjunctions, and the conjunctions include logical conjunctions and / or temporal conjunctions.

[0162] In one possible implementation, the logical connectives include one or more of the following:

[0163] Negation, conjunction, disjunction, deduction, equivalence.

[0164] In a possible implementation, the temporal connectives include one or more of the following:

[0165] Until, always, eventually.

[0166] Please refer to FIG. 4 , which is a schematic structural diagram of another possible data processing device 40 provided in an embodiment of the present application.

[0167] The data processing device 40 can be an independent device such as a vehicle, a drone, a robot, or a device included in an independent device, such as a chip, a software module, or an integrated circuit. The data processing device 40 may include at least one processor 401 and a communication interface 402. Optionally, it may also include at least one memory 403. Further optionally, it may also include a connection line 404, wherein the processor 401, the communication interface 402 and / or the memory 403 are connected via the connection line 404, and communicate with each other via the connection line 404 to transmit control and / or data signals. Wherein:

[0168] (1) The processor 401 is a module that performs arithmetic operations and / or logical operations, and may specifically include one or more of the following devices: CPU, MCU, AP, TDC, filter, GPU, MPU, ASIC, ISP, DSP, FPGA, CPLD, coprocessor (to assist the central processor in completing corresponding processing and applications), and / or NPU, etc.

[0169] (2) The communication interface 402 can be used to provide information input or output for the at least one processor. In some possible scenarios, the communication interface 402 may include an interface circuit. And / or, the communication interface 402 can be used to receive data sent from the outside and / or send data to the outside. For example, the communication interface 402 may include a wired link interface such as an Ethernet cable, or a wireless link (Wi-Fi, Bluetooth, general wireless transmission, vehicle-mounted short-range communication technology, or other short-range wireless communication technology, etc.) interface. Optionally, the communication interface 402 may also include a transmitter (such as a radio frequency transmitter, or an antenna, etc.) coupled to the interface, or a receiver, etc.

[0170] Alternatively, if the data processing apparatus 40 is a standalone device, the communication interface 402 may include a receiver and a transmitter. The receiver and the transmitter may be the same component or different components. When the receiver and the transmitter are the same component, the component may be referred to as a transceiver.

[0171] Optionally, if the data processing device 40 is a chip or a circuit, the communication interface 402 may include an input interface and an output interface. The input interface and the output interface may be the same interface, or may be different interfaces.

[0172] Optionally, the functions of the communication interface 402 may be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 401 may be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

[0173] (3) Memory 403 is used to provide storage space, which can store data such as operating systems and computer programs. Memory 403 can be one or a combination of random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0174] The functions and actions of the modules or units in the data processing device 40 listed above are merely exemplary.

[0175] Each functional unit in the data processing device 40 can be used to implement the aforementioned data processing method, such as the method described in the embodiment shown in Figure 1. To avoid redundancy, detailed descriptions thereof are omitted here.

[0176] Optionally, processor 401 may be a processor specifically used to execute the aforementioned method (for convenience of distinction, referred to as a dedicated processor), or a processor that executes the aforementioned method by calling a computer program (for convenience of distinction, referred to as a dedicated processor). Optionally, the at least one processor may include both a dedicated processor and a general-purpose processor.

[0177] Optionally, in the case where the computing device includes at least one memory 403 , if the processor 401 implements the aforementioned method by calling a computer program, the computer program may be stored in the memory 403 .

[0178] In one possible design, the data processing device 40 is used to implement the aforementioned electronic device method, wherein the processor 401 in the data processing device 40 is used to perform the following operations:

[0179] Acquire a first description text in a first description language, where the first description text represents a first element of the smart terminal in a first scenario;

[0180] Obtaining a second description text in a second description language, where the second description text represents the first element, and the description name and parameter type of the first element represented by the first description text are the same as the description name and parameter type of the first element represented by the second description text;

[0181] The first description text and the second description text are executed.

[0182] In a possible implementation, the first element belongs to a predefined first element library;

[0183] The obtaining of the first description text in the first description language includes:

[0184] The first description text is acquired according to the first scene and the first element library.

[0185] In a possible implementation, the first element belongs to a predefined second element library;

[0186] The obtaining of the second description text in the second description language includes:

[0187] The second description text is acquired according to the first scene and the second element library.

[0188] In a possible implementation, the description name, parameter type, and parameter value of the first element represented by the first description text are the same as the description name, parameter type, and parameter value of the first element represented by the second description text.

[0189] In a possible implementation, the first description language is different from the second description language, and the first description language or the second description language includes:

[0190] Design operation scope ODD description language, static scenario description language, dynamic scenario description language, or verification and evaluation description language.

[0191] In a possible implementation, the ODD description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements; or

[0192] The static scene description language describes one or more of the following types of elements: road elements; or

[0193] The dynamic scene description language describes one or more of the following types of elements: environment elements, vehicle status elements; or

[0194] The verification and evaluation description language describes one or more of the following types of elements: road elements, environment elements, and vehicle status elements.

[0195] In a possible implementation manner, the first element includes one or more elements.

[0196] In a possible implementation, the first element includes multiple elements, and the multiple elements are connected by conjunctions, and the conjunctions include logical conjunctions and / or temporal conjunctions.

[0197] In one possible implementation, the logical connectives include one or more of the following:

[0198] Negation, conjunction, disjunction, deduction, equivalence.

[0199] In a possible implementation, the temporal connectives include one or more of the following:

[0200] Until, always, eventually.

[0201] The present application also provides a chip system, which includes a processor and a communication interface, wherein the communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output to the processor. The chip system is used to implement the aforementioned data processing method, such as the method described in FIG1.

[0202] Optionally, an embodiment of the present application provides an autonomous driving simulation system that can execute the method described in FIG. 1 above to implement simulation testing of an intelligent driving terminal (e.g., an autonomous driving vehicle) equipped with an intelligent driving system. Optionally, the autonomous driving simulation system can be deployed in a server, cloud platform, electronic device, host computer, etc. Alternatively, the autonomous driving simulation system can be deployed in a chip in an electronic device, etc., without limitation herein.

[0203] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions. When the instructions are executed on at least one processor, the aforementioned data processing method, such as the method described in FIG1 , is implemented.

[0204] An embodiment of the present application further provides a computer program product, which includes computer instructions and, when executed by a computing device, implements the aforementioned data processing method, such as the method described in FIG1 .

[0205] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0206] The “at least one” mentioned in the embodiments of this application refers to one or more, and “plurality” refers to two or more. “At least one of the following items” or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, c can be single or multiple. “And / or” describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character “ / ” generally indicates that the previous and next associated objects are in an “or” relationship.

[0207] Furthermore, unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, timing, priority, or importance of multiple objects. For example, the first device and the second device are only for ease of description and do not indicate differences in structure, importance, etc. between the first and second devices. In some embodiments, the first device and the second device can also be the same device.

[0208] In the above embodiments, the term "when" can be interpreted to mean "if...", "after...", "in response to determining...", or "in response to detecting...", depending on the context. The above are merely optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the concepts and principles of the present application shall be included in the scope of protection of the present application.

[0209] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

Claims

1. A data processing method, characterized in that: include: Acquire a first description text in a first description language, where the first description text represents a first element of the smart terminal in a first scene; Acquire a second description text in a second description language, where the second description text represents the first element, and a description name and a parameter type of the first element represented by the first description text are the same as a description name and a parameter type of the first element represented by the second description text; The first description text and the second description text are executed.

2. The method according to claim 1, characterized in that The first element belongs to a predefined first element library; The step of obtaining a first description text in a first description language includes: The first description text is acquired according to the first scene and the first element library.

3. The method according to claim 1 or 2, characterized in that: The first element belongs to a predefined second element library; The step of obtaining a second description text in a second description language includes: The second description text is acquired according to the first scene and the second element library.

4. The method according to any one of claims 1 to 3, characterized in that: The description name, parameter type and parameter value of the first element of the first description text representation are the same as the description name, parameter type and parameter value of the first element of the second description text representation.

5. The method according to any one of claims 1 to 4, characterized in that: The first description language is different from the second description language, and the first description language or the second description language includes: Design operation scope ODD description language, static scenario description language, dynamic scenario description language, or verification and evaluation description language.

6. The method according to claim 5, characterized in that The ODD description language describes one or more of the following types of elements: road elements, environment elements, vehicle status elements; or, The static scene description language describes one or more of the following types of elements: road elements; or The dynamic scene description language describes one or more of the following types of elements: environment elements, vehicle status elements; or, The verification and evaluation description language describes one or more types of elements: road elements, environment elements, and vehicle status elements.

7. The method according to any one of claims 1 to 6, characterized in that: The first element includes one or more elements.

8. The method according to claim 7, characterized in that The first element includes a plurality of elements connected by connectives, wherein the connectives include logical connectives and / or temporal connectives.

9. The method according to claim 8, characterized in that The logical connectives include one or more of the following: Negation, conjunction, disjunction, deduction, equivalence.

10. The method according to claim 8 or 9, characterized in that: The temporal connectives include one or more of the following: Until, always, eventually.

11. A data processing device, characterized in that: include: An acquiring unit, configured to acquire a first description text in a first description language, wherein the first description text represents a first element of the smart terminal in a first scene; The acquiring unit is configured to acquire a second description text in a second description language, wherein the second description text represents the first element, and the description name and parameter type of the first element represented by the first description text are the same as the description name and parameter type of the first element represented by the second description text; A processing unit is used to execute the first description text and the second description text.

12. The device according to claim 11, characterized in that The first element belongs to a predefined first element library; When acquiring the first description text in the first description language, the acquiring unit is used to: The first description text is acquired according to the first scene and the first element library.

13. The device according to claim 11 or 12, characterized in that The first element belongs to a predefined second element library; When acquiring the second description text in the second description language, the acquiring unit is used to: The second description text is acquired according to the first scene and the second element library.

14. The device according to any one of claims 11 to 13, characterized in that: The description name, parameter type and parameter value of the first element of the first description text representation are the same as the description name, parameter type and parameter value of the first element of the second description text representation.

15. The device according to any one of claims 11 to 14, characterized in that: The first description language is different from the second description language, and the first description language or the second description language includes: Design operation scope ODD description language, static scenario description language, dynamic scenario description language, or verification and evaluation description language.

16. The device according to claim 15, characterized in that The ODD description language describes one or more of the following types of elements: road elements, environment elements, vehicle status elements; or, The static scene description language describes one or more of the following types of elements: road elements; or The dynamic scene description language describes one or more of the following types of elements: environmental elements, vehicle status elements, state element; or, The verification and evaluation description language describes one or more types of elements: road elements, environment elements, and vehicle status elements.

17. The device according to any one of claims 11 to 16, characterized in that: The first element includes one or more elements.

18. The device according to claim 17, characterized in that The first element includes a plurality of elements connected by connectives, wherein the connectives include logical connectives and / or temporal connectives.

19. The device according to claim 18, characterized in that The logical connectives include one or more of the following: Negation, conjunction, disjunction, deduction, equivalence.

20. The device according to claim 18 or 19, characterized in that The temporal connectives include one or more of the following: Until, always, eventually.

21. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 10.

Images