Automated data entry and error check method for generating state transition tables
Through auxiliary design toolbox and data entry methods, the states and events in the finite state machine model are automatically identified and verified, and the omissions and inconsistencies in complex systems are solved, a complete and accurate state transition table is realized, and the system design quality is improved .
Patent Information
- Application Number
- CN202311403584.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-16
- Filing Date
- 2023-10-26
- Publication Date
- 2024-11-22
AI Technical Summary
When designing finite state machine models of complex systems, it is difficult for the prior art to fully identify and verify all possible states, state transitions and events, resulting in omissions and inconsistencies, affecting the performance and quality of the system.
Through an auxiliary design toolbox and data entry method, system features, such as states, events and super events, automatically generate an initial state transition table, and fill it with user input, check the state transition table using predetermined error check criteria, identify and Key features of the alarm missing until no omissions are output, and the final state transition table is output.
Ensure the integrity and consistency of the finite state machine model, help designers to fully understand system behavior, avoid omissions and inconsistencies, and improve the design quality and performance of the system.
Smart Images

Figure CN119003040A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a software-based design toolkit and data entry method for assisting a designer, programmer, or other user in designing and verifying systems modeled as finite state machines, particularly those systems having complex behavioral characteristics. Background Art
[0002] As those skilled in the art will appreciate, a finite state machine is a mathematical abstraction that is often used to design and verify the expected behavior of countless different software programs and physical systems. A finite state machine can be graphically represented as a state diagram with an initial state, one or more additional states, associated state transitions, and various inputs or events. Based on the current state of the modeled system and a given event or combination of events, the finite state machine performs one or more of these state transitions. The finite state machine can be programmed and executed in software, and the corresponding state transition table captures the above states, state transitions, and triggers events. The state transition table is then used as a performance model of the underlying system. Summary of the invention
[0003] An automated system and related methods for assisting a user (e.g., a software programmer, designer, or system developer) in the design of a finite state machine (FSM) model of an underlying system are disclosed herein. The methods contemplated herein are particularly suitable for modeling systems with complex behavioral characteristics, such as various possible states, state transitions, events, and other possible characteristics as described above. For example, a motor vehicle with automated control capabilities has complex modes and conversion rules. Some of these modes are automatically executed or executed in response to driver input, while other modes are based on timers, hidden logic, or other automatically occurring activation criteria. Due to this complexity and the critical state of the modeled system to be understood as close to perfect as possible, it is necessary to verify whether the underlying system and the associated human-machine interface are designed correctly and completely. The present solution enables the identification of omissions and inconsistencies in the finite state model, as well as locations or conditions where the finite state model is not fully specified.
[0004] To this end, a method for guiding or assisting a user in modeling a system is disclosed herein. An embodiment of the method includes receiving system features through a host computer, the system features including system states, events, super events (event combinations), hierarchy definitions, state transitions, and possible other system features. The method includes generating an initial state transition table in response to the system features, the action occurring through the host computer. The finite state table is indexed with a complete population of possible states and events of the system modeled by the FSM, and is partially populated with system features entered by a user. An embodiment of the method also includes populating the initial state transition table through the host computer in response to a set of user inputs. The action includes automatically generating a populated state transition table.
[0005] The method may include error checking the populated state transition table using predetermined error checking criteria, including searching the populated state transition table for missing state transitions by the host computer. The host computer may transmit an alert to a user in response to the missing state transitions. Additional error checking functionality within the scope of the present disclosure may include: verification of state transitions for each event type belonging to a state of a particular container as described herein; and highlighting of critical events and states to help identify critical event to non-critical event transitions, and generally, to more thoroughly review such highlighted transitions.
[0006] A non-limiting representative implementation of the method includes receiving system characteristics from a user via the host computer, the system characteristics including states, state transitions, and events of the modeled system. The method also includes generating (via the host computer) an initial state transition table in response to receiving the system characteristics, the initial state transition table being partially populated by the system characteristics, and populating the initial state transition table via the host computer in response to a set of user inputs from a user of the host computer, thereby automatically generating a populated state transition table. In addition, the method includes error checking the populated state transition table using predetermined error checking criteria, including searching the populated state transition table for missing key features of the modeled system via error checking logic of the host computer. An alert may then be transmitted to a user of the host computer in response to the missing key features.
[0007] Receiving the system characteristics may include receiving user-initiated events, system-triggered events, and timeout events of the modeled system.
[0008] The method may further include iteratively executing the method until the host computer does not detect the missing key feature, and then outputting the populated state transition table as a final state transition table once the host computer does not detect the missing key feature.
[0009] An embodiment of the method includes: presenting a menu of possible states and events of the modeled system to a user via a display screen of the host computer; and determining the system characteristics via the host computer using touch or keyboard input. The method may optionally include displaying the menu as a drop-down list. In such an embodiment, receiving the system characteristics includes recording a user entry or selection from the drop-down list.
[0010] One aspect of the present disclosure includes: receiving, by the host computer, one or more containers of meaning in which two or more of the states are grouped together; and converting the containers into a state hierarchy. The method may also include: displaying an intuitive drag-and-drop graphic or editing tool to a user via a display screen of the host computer; and also receiving the one or more meaning containers as a user response to the drag-and-drop graphic or editing input from the editing tool. Aspects of the method may include confirming, by the host computer, the validity of the state transition of each event type in each corresponding container of the containers. A validity confirmation status may also be transmitted to the user in response to confirming the validity of the state transition of each event type.
[0011] In one possible implementation, the method may include receiving a user-defined composite event as a combination of the events, and then updating the populated state transition table with the user-defined composite event.
[0012] Another possible implementation of the method includes receiving, by the host computer, a customized event query from a user, the customized event query describing one or more hypothetical combinations of the events. The method may also include: determining, by the host computer, a result of the event query; and updating the populated state transition table with the result.
[0013] Another aspect of the present disclosure includes a modeling system for generating a populated state transition table for a modeled system. An embodiment of the modeling system includes a host computer having a non-transitory computer-readable storage medium ("memory") and a processor, wherein the memory includes an instruction set executable by the processor. A display screen is in communication with the host computer. Execution of the instruction set by the processor causes the host computer to: receive system characteristics from a user of the host computer, including states, state transitions, and events of the modeled system, and generate (by the host computer) an initial state transition table in response to receiving the system characteristics, the initial state transition table being partially populated by the system characteristics. Execution of the instruction set also causes the processor to: populate the initial state transition table in response to a set of user inputs, thereby automatically generating a populated state transition table; error check the populated state transition table using a predetermined error checking criterion, which includes searching the populated state transition table for missing key features of the modeled system by the error checking logic of the host computer; and transmit an alert to the user of the host computer in response to the missing key features or transmit the results of the event query to the user.
[0014] Another aspect of the disclosure may include execution of the set of instructions by the processor causing the host computer to: receive system characteristics as user-initiated events, automatically occurring events, external events, and fault-triggered events of the modeled system.
[0015] Another aspect of the present disclosure may include execution of the set of instructions by the processor causing the host computer to: iteratively perform a method until the host computer detects no missing critical feature, the method comprising receiving the system feature, generating the initial state transition table, populating the initial state transition table, error checking the populated state transition table, and transmitting an alert to a user; and once the host computer detects no missing critical feature, outputting the populated state transition table as a final state transition table.
[0016] Another aspect of the present disclosure may include execution of the set of instructions by the processor causing the host computer to: present a menu of possible states and events of the modeled system to a user via a display screen of the host computer, including displaying the menu as a drop-down list; determine the system characteristics via the host computer using touch or keyboard input; and record a user entry or selection from the drop-down list in response to the touch or keyboard input.
[0017] A computer-readable storage medium is also disclosed herein, on which instructions executable by a processor are recorded. Execution of the recorded instructions enables the processor to perform the above steps.
[0018] The above-mentioned features and advantages of the present disclosure and other features and attendant advantages will become apparent from the following detailed description of illustrative examples and modes for implementing the present disclosure when considered in conjunction with the accompanying drawings and the appended claims. In addition, the present disclosure expressly includes combinations and sub-combinations of the elements and features presented above and below. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate embodiments of the present disclosure and are used together with this description to explain the principles of the present disclosure. The accompanying drawings are not necessarily drawn to scale and may present slightly simplified representations of various preferred features of the present disclosure as disclosed herein, including, for example, specific sizes, orientations, positions, and shapes. Details related to such features will be determined in part according to specific intended applications and use environments.
[0020] Figure 1 A modeling system for finite state modeling of an underlying system is shown, wherein the modeling system is configured to perform data entry and automatic error checking methods when creating a state transition table.
[0021] Figure 1A Shown is a method for implementing Figure 1 An exemplary embodiment of a distributed processing node of a modeling system.
[0022] Figure 2 An exemplary screen shot of the event definition phase of the method described herein is shown, wherein the event / input is represented by Figure 1 The representative modeling system depicted in is defined by the user.
[0023] Figure 3 Shown is the method for executing Figure 2 Another exemplary screen for the event definition phase of FIG.
[0024] Figure 4 Possible screens for the state definition phase according to an exemplary method are shown.
[0025] Figure 5 FIG. 1 shows an example of a method for grouping states into different meaning containers according to one aspect of the present disclosure. Figure 1 The functionality of the modeling system.
[0026] Figure 6 Depicts possible implementations of the composite / super event definition phase that can be used as part of this strategy.
[0027] Figure 7 is a simplified representative state transition table according to one aspect of the present disclosure.
[0028] Figure 8 Shown by Figure 1 Possible ways to implement customized queries in a modeling system.
[0029] Fig. 9 Is to describe the use Figure 1 A flow chart of an embodiment of a modeling system for data entry and automatic error checking. DETAILED DESCRIPTION
[0030] The present disclosure may be implemented in many different forms. Representative examples of the present disclosure are shown in the accompanying drawings and are described in detail herein as non-limiting examples of the disclosed principles. For this reason, elements and limitations described in the abstract, technical field, background technology, summary of the invention, and detailed description but not explicitly stated in the claims should not be incorporated into the claims individually or collectively by implication, inference or otherwise.
[0031] Referring to the drawings, wherein like reference numerals refer to like features throughout the several views, Figure 1 A computerized modeling system 10 for performing data entry and automatic error checking during the design of a finite state model (FSM) is depicted. Figure 1The modeling system 10 includes a host computer 12, such as a laptop computer, tablet computer, desktop computer, mobile application ("app"), etc., configured to assist a designer, programmer, or another user 11 in modeling a complex hardware and / or software-based system ("FSM-modeled system"). Although the host computer 12 is depicted as a single device for simplicity of illustration, those skilled in the art will appreciate that the host computer 12 can be implemented as a distributed host computer system 120 having multiple processing nodes (e.g., 12A, 12B, ..., 12N), such as Figure 1A Such processing nodes may communicate with each other via suitable wired or wireless networking connections. The modeling system 10 may be used to model the performance of a human-machine interface ("HMI") or another device onboard a motor vehicle or aircraft, ship, rail vehicle, or another dynamic system, or to model the performance of a medical device, power equipment, or another static system.
[0032] Figure 1 The modeling system 10 may include one or more peripheral devices 13, including a display screen 14 operable as an output device of the host computer 12. When developing or designing state transition tables for a system modeled with an FSM (including the functionality of its resident software and / or hardware), a user 11 may interact with the host computer 12 via one or more additional peripheral devices 13 (not shown), such as a mouse, keyboard, touch input to the display screen 14, etc.
[0033] As understood in the art, when designing a FSM model suitable for an application, the task faced by the user 11 is often complicated by the high complexity of the system modeled with the FSM. For example, although the operation of a binary system such as an on / off desk lamp can be represented by its two possible states ("on" and "off"), two possible state transitions ("on-off" and "off-on"), and two inputs or events ("switch is turned off" and "switch is turned on"), accurate FSM modeling of more complex systems may require the same user 11 to consider hundreds or thousands of different states, state transitions, events, and other possible system features. Therefore, the user 11 may inadvertently ignore or omit one or more states, state transitions, or event combinations ("super events"), which in turn may reduce the performance and quality of the modeled system. Therefore, the present solution is intended to facilitate the design and development of FSMs and corresponding state transition tables, so as to allow the user 11 to fully define possible states, set the hierarchy of such states in an intuitive manner, and ultimately build the state transition table in a comprehensive manner and test it for errors. In addition to the many benefits that may accompany the present solution, the user 11 is guided to consider functionally critical states by highlighting potential errors or omissions ("critical features"). As described above, additional error checking functionality may be provided within the scope of the present disclosure, including validation of state transitions for each event type belonging to a state of a particular container as described below, and highlighting of critical events and states to help identify transitions of critical events to non-critical events, and generally, to more thoroughly review such highlighted transitions.
[0034] As part of this strategy, Figure 1 The host computer 12 or Figure 1A Its constituent processing nodes 12A, 12B, ..., 12N may be equipped with an error checking module ("ECM") 52, a non-tangible computer readable storage medium or memory (M) 54, and one or more processors (P) 53, such as logic circuits, (one or more) combinational logic circuits, (one or more) application-specific integrated circuits (ASICs), (one or more) electronic circuits, (one or more) central processing units, semiconductor IC devices, etc., and (one or more) input / output (I / O) circuits, appropriate signal conditioning and buffering circuits, and other components such as high-speed clocks to provide the described functions. The associated memory 54 may include a number and type of non-transitory memory suitable for the application, including read-only, programmable read-only, random access, hard disk drives, etc., whether resident, remote, or a combination of both.
[0035] As described herein, the host computer 12 is configured to receive system characteristics 15 from the user 11. This may entail receiving various states, state transitions and events of the system being modeled, as well as possible super events (event combinations), hierarchy definitions and other system characteristics 15. In response to the received system characteristics 15, the host computer 12 automatically generates and outputs an initial state transition table (TST) containing blank / unpopulated state transition tables. i ) 19. The initial state transition table 19 is indexed by a population of possible states and events of the modeled system that is as complete as possible, and has the system characteristics 15 entered by the user 11. In addition, the host computer 12 automatically fills the initial state transition table 19 with the second data set 18, thereby generating a third data set 19S, which includes the populated state transition table (T P )20.
[0036] That is, the host computer 12 automatically generates a populated state transition table 20 as a third data set 19S. This occurs in response to a set of user inputs 16. Fig. 9 After one or more iterations of the state transition table (T F ) 21. The final state transition table 21 is then used as needed, typically as a starting point for further research by the user 11 and as a basis for developing state diagrams and scenario simulations for the system being modeled.
[0037] As part of the disclosed solution, Figure 1 The host computer 12 schematically shown in FIG. 1 processes the third data set 19S through the ECM 52 to error check the populated state transition table 20. This action occurs using predetermined error checking criteria. For example, the host computer 12 may search the populated state transition table 20 for missing critical features, such as missing states, state transitions, events, and / or (one or more) other features of system-critical or functionally critical components of the modeled system. As part of this strategy as described below, the host computer 12 may also send an alarm signal (CC 22 ) is transmitted to the display screen 14 or an external device 22, such as a smart phone or Figure 1A Such action occurs in response to the missing key feature at one of the various processing nodes 12A, 12B, ..., 12N.
[0038] Additional error checking functionality may be included, such as the above-described validation of state transitions for each event type belonging to a particular container's state as described herein, and highlighting of critical events and states to help identify transitions of critical events to non-critical events. Fig. 9A non-limiting exemplary implementation or method 100 according to the present teachings is shown. Those skilled in the art having the benefit of the foregoing disclosure will appreciate that the method 100 and the execution thereof by the host computer 12 provide improvements in computer-related techniques related to FSM-based modeling of systems and related functions. Such improvements are achieved in part by enabling computers to perform functions that were previously not able to be performed in this capacity. Figures 1 to 8 The specific solution described achieves the desired result of a complete and error-checked state transition table (i.e., the final state transition table 21). Reference will now be made to Figures 2 to 8 The various stages that make up method 100 are described below.
[0039] Defining events: Now refer to Figure 2 As part of this method, Figure 1 The display screen 14 of the embodiment presents a representative event input screen 30 to the user 11. The purpose of this particular step is to appropriately define the events in the system being modeled. To this end: (1) the events are organized into one of three categories: (i) user initiated; (ii) system triggered; and (iii) timeout; (2) the event type will be (i) user event (for the user initiated category), (ii) machine state, sensor state, environmental condition, external event, etc. (for the system triggered category) or (iii) user ready, triggered timer and independent timer (for the timeout event category). Finally, (3) the values have (i) deterministic values, such as strings of text and / or numbers, (ii) Boolean values, i.e. true or false, or (iii) integers, including logical properties such as ≥, <, =, etc.
[0040] Before the user 11 enters the system features 15, the host computer 12 may first present an input screen 30 as a set of user selectable buttons. For example, the user 11 may add a new event via the event name button 31. Figure 2 The button is labeled "Speed" in the example to describe the non-limiting example event where the system being modeled is a motor vehicle. Event description button 310 may be used to further define the event. Value category button 320 (e.g., "Certainty" as shown) may be presented in Figure 2 10 is a representative "Add Event" screen. The user 11 may then define the event type via the event type button 32 and event subtype button 420 (e.g., as shown in the "User Input" figure), and select the add or "+" action via the corresponding selection button 33. The value button 34 may be selected to add the corresponding possible values, e.g., Figure 2 "0mph", "In Range", and "Over Speed" in the example shown.
[0041] The input screen 30 may also present several event category buttons 35 to enable the user 11 to define whether a given event is a user-initiated category as described above or occurs automatically, such as in response to a timer, external / environmental, fault-triggered, etc. The different categories may be assigned a given line width / style (dashed, solid, dotted, etc.) or color, which is then used to connect the states in the corresponding state transition diagram. Additional buttons may be used with Figure 2 The input screen 30 is used together with other purposes, such as but not limited to an add new event button 36 and a clear event field button 37.
[0042] In general, Figure 2 The buttons 31 to 37 in the non-limiting embodiment allow Figure 1 The user 11 initially defines an event or input for Figure 1 The host computer 12 is used in constructing a state transition diagram of the modeled system. The method 100 may include presenting a menu of possible states and events of the modeled system via the display screen 14, which menu may be configured to receive touch or keyboard input from the user 11, and then using such touch or keyboard input to determine the above-mentioned system characteristics 15. This may include displaying the menu as a drop-down list, in which case receiving the system characteristics 15 includes recording the user entry or selection from the drop-down list, for example, in the memory 54 of the host computer 12. The user 11 may also restrict the values according to their appropriateness to the above-mentioned value categories.
[0043] Brief reference Figure 3 Representative event table screen 40, in response to using Figure 2 The host computer 12 can complete the data entry by Figure 1 The display screen 14 presents a representative event screen 40. As described above, possible event values include deterministic values, Boolean values, and integers. To this end, the event table screen 40 may include corresponding Figure 2 The event screen 40 may further include a column of buttons such as an event name button 31, an event type button 32, a possible value button 34, and an event kind button 35. The event screen 40 may also include a selection box 41 corresponding to each event name, such as symbolic events E1, E2, ..., EN.
[0044] Non-limiting exemplary event types for a representative modeled system include user events (for the user-initiated category), machine states, sensor states, environmental conditions, external events, etc. (for the system-triggered event category), or user ready, triggered timers, and independent timers for timeout events, as described above. As an illustration of some of these events, "time" represents a symbolic timeout event E1, "user input" represents a symbolic user event E2, and "external" represents the Nth symbolic event EN, such as an external event or an environmental event. In this representative case, the possible values 34 of the symbolic event E1 can be one or more time thresholds or ranges, such as the illustrated example ranges of <5s, 5s≤t≤20s, and >20s, or a true or false (T, F) range for the symbolic event E2, or "OK, not OK" for the symbolic event EN. For example, exemplary category events that can be entered by the user 11 through the category (or event) button 35 can include "user initiated", "system triggered" (as shown in the figure), or "timeout". Therefore, the representative event screen 40 can present events for each state transition, Figure 1 The user 11 can edit from the event screen 40 simply by adding, deleting or modifying one or more rows.
[0045] Define the state: Figure 4 As shown, the possible states of a system modeled as a finite state system can be given by Figure 1 11 using the host computer 12. In a non-limiting illustrative example, the user 11 can view and select from a "List + Label States" column 42 having a primary selection button 42A, from which the user 11 can select or enter a plurality of states 42B, such as symbolic states A, B, ..., N, the identity of the states depending on the application as understood in the art. An "Add Description" column 43 having a primary selection button 43B enables the user 11 to select one or more corresponding state descriptions 43B, labeled as symbolic state descriptions D1, D2, D3, D4, ..., DN. For example, continuing with the non-limiting example of a motor vehicle as the system being modeled, such descriptions may include "Available" (or "Standby"), "Active", "Upgraded", etc. In addition, the user 11 can utilize an "Add Key Function" column 44 having a primary selection button 44A to define key functions or impacts 44B, labeled as symbolic functions FC1 and FC2, such as the response level of the end user or system.
[0046] Still reference Figure 4 , Figure 1The user 11 may also view and edit an "Actual Behavior" column 45 with a corresponding primary selection button 45A to define behaviors 45B, such as symbolic user behaviors BA1, ..., BAN and / or symbolic system behaviors BS1, ..., BSN. Representative user behaviors in the same subject matter as the motor vehicle illustrative example outlined above may include "full control", "lateral control", "longitudinal control", "no control", etc., and representative system behaviors may include, for example, "maintain speed", "coast", or "intelligent deceleration" and many other possible application-specific behaviors. In addition to columns 42, 43, 44 and 45, Figure 1 The user 11 shown in FIG. 4 can assign characteristics 46B using the "Assign Characteristics" column 46 and the primary selection button 46A. Such characteristics can be arranged into different types, such as visual characteristics (V) 46B1, auditory characteristics (A) 46B2, and tactile characteristics (H) 45B3, each characteristic type having one or more selected characteristics.
[0047] For example, user 11 may select a specific list of symbolic visual characteristics, V1, V2, ..., VN, for visual characteristics 46B1, such as "color", "saturation", "amplitude", "envelope shape", etc. Similarly, auditory characteristics 46B2 may include symbolic auditory characteristics A1, A2, ..., AN, such as "timbre", "frequency", "envelope shape", "directivity", etc. Tactile characteristics 46B3 may include symbolic tactile characteristics H1, H2, ..., HN. Thus, user 11 is able to define various system states for use by host computer 12 in generating one or more state transition tables and iteratively error checking and updating them.
[0048] Status Grouping: Reference Now Figure 5 , Figure 1 The host computer 12 depicted in FIG. 1 may then present to the user 11 a complete list of previously selected system states 55, which for simplicity are labeled as symbolic states A through I. In this representative implementation, each of the states 55 has a corresponding selection box 550, which, when selected, allows the user 11 to select and manipulate the state 55 into a desired hierarchy. In one or more embodiments, the host computer 12 receives a user-defined meaning container ("container") from Figure 4 Two or more states 55 of are grouped together in a meaning container. Then, the host computer 12 can transform the container assigned by the user into a corresponding state hierarchy.
[0049] To facilitate this alternative method, the host computer 12 may be configured to Figure 1The display screen 14 is shown displaying an intuitive drag-and-drop graphic 56, for example, as rectangular containers C1, C2, C3, and C4. The host computer 12 may then group one or more of the illustrated example containers C1, C2, C3, and / or C4 as a user response to the drag-and-drop graphic 56. For example, in Figure 5 The exemplary states 55, symbolically labeled K, I, and J in the diagram, may be arranged into container C3, container C1 containing containers C2 and C3, container C2 including (empty) container C4. Thus, the user 11 may build up a hierarchy of states in an intuitive manner, including functions such as "delete" and "add" via corresponding buttons 56D and 56A to add and delete new containers. Adding or deleting states to / from containers may be performed using a "drag and drop" function, or perhaps using typical cut, copy, and paste editing tool functions. The host computer 12 may also confirm the validity of the various state transitions for each event type in each corresponding container as a container of the added function, and thereafter transmit the validity confirmation status to the user 11, for example as a Figure 1 Warning signal (CC 22 ) that occurs in response to confirming the validity of a state transition.
[0050] Defining a super event: According to the present disclosure Figure 1 The user 11 may also combine multiple inputs or events, such as concurrent user-generated, automatically-generated, or environment-generated / externally-generated events. The action may entail receiving a user-defined composite event or "super event" by the host computer 12 that is a combination of two or more previously defined events. For example, the user 11 may notice that the modeled system is able to transition to a new state (such as from Figure 5 As an example, even if all other conditions for transitioning from state A to state B are satisfied, in the exemplary motor vehicle use case, a “camera blocked” condition may prevent the modeled system from transitioning to “autopilot mode.” According to one aspect of the present disclosure, the host computer 12 may then update the composite event with the user-defined composite event. Figure 1 The populated state transition table 20.
[0051] refer to Figure 6 , the above super event can be represented by Figure 1A user 11 of the host computer 12 uses yet another user screen 58 to construct. Here, the user 11 can define a super event name such as "Automatic Activity", add or remove event types using the corresponding "+" or "-" buttons, and define the (one or more) event types associated with each new super event. For example, symbolic event types T1, T2, ..., TN may be collectively considered to be part of the "Automatic Activity" super event, with assigned symbolic event names N1, N2, ..., NN and associated values such as "false" or "true", "yes", etc. Therefore, as part of the present method, the user 11 may use the screen 58 shown to assist in the development of one or more super events, which will enable automated error checking functionality while avoiding conflicts or race conditions. The user 11 is also free to explore possible event proliferation and export the results to Figure 1 The updated state transition table 20. This approach will also highlight interesting interactions between key events.
[0052] Generate state transition table: reference Figure 7 , Figure 1 The various state tables 19, 20 and 21 schematically shown in FIG. 1 can be visualized as a simplified state transition table 60. In this exemplary illustration, the state transition table 60 is organized into a row of symbolic states 64, e.g., A, B, C, ..., ZZ for simplicity, and an "event" column 62 containing symbolic events E1, E2, E3, ..., EN, where the events are referred to above. Figure 2 and Figure 3 Each event in column 62 may in turn trigger a transition to a corresponding state in column 63. For example, in the illustrated state transition table 60, event E2 occurring in state A may cause the modeled system to transition to state E. As part of the present method, each state defined by the user 11 is listed in the exemplary state transition table 60.
[0053] In one possible approach, when displayed in Figure 7 When the state transition table 60 is displayed, the super events as described above can be color coded to distinguish them from regular events. In addition, the user 11 can access the state transition table 60 and edit it directly, such as in response to a request from Figure 1The host computer 12 may provide a prompt indicating a missing critical state, state transition, or event. That is, the host computer 12 may allow the user 11 to edit the state transition table 60 from within, for example, by opening a drop-down menu in response to the user 11 selecting a particular state or event from the state transition table 60. For simplicity, this functionality is illustrated at the symbolic event E3 by its framed outline and the designation "manual" or "M" indicating the possibility for the user 11 to edit or enter the corresponding state into the state transition table 60. Thus, the user 11 is guided when constructing, populating, error checking, and updating the state transition table 60, and these actions are described below with reference to Fig. 9 The described method 100 occurs iteratively.
[0054] Figure 1 The host computer 12 can display Figure 7 After the state transition table 60, missing key states or other key features are highlighted, and the user 11 is prompted to resolve any states that may be missing in the initial definition. For example, Figure 1 The ECM 52 depicted in FIG. 5 can be used for this purpose to enable the host computer 12 to automatically check whether the state transition table 60 lacks consistency and / or completeness. As part of this possible implementation, the host computer 12 can be configured to check the validity of the various state transitions for each event type as described above, and to check the state belonging to one or more specific containers (see FIG. Figure 5 ). Highlighting key events and key states will help the user 11 correctly identify state transitions from key states to non-key states in response to various events. Also note that filters can be used, or tags for key events, key states, and their intersections, as well as the ability to edit events and super events from the page, etc.
[0055] Customized queries: As part of this approach, Figure 1 The user 11 of the host computer 12 depicted in FIG. 1 can also perform customized queries. This capability enables the design and development of finite state models to be Figure 7 The state transition table 60 of the system is further stress-tested, thereby allowing the user 11 to explore the countless possible combinations of events that the modeled system could conceivably encounter during actual operation. This may include receiving a customized event query from the user 11 via the host computer 12, the customized event query describing one or more hypothetical combinations of events. The host computer 12 may determine the results of the event query and update the Figure 1 The populated state transition table 20.
[0056] To this end, Figure 8, having add and delete buttons 71 (+, -), an "event type" button 72, an "event name" button 73, and a "value" button 74. Using the query screen 70 or a similar interface, the user 11 can construct multiple combinations of events, either individually, in a specific order, or as a super event as described above. The user 11 can select a combination of interest, name it, and save it as a new row in the state transition diagram. The host computer 12 can then update the state transition table 60 ( Figure 7 ), which the user 11 may thereafter review and evaluate for the missing key features as described above. This approach will help guide the user 11 in the direction of the overlooked or omitted features, at least some of which may be considered functionally key features and therefore merit one or more specific entries in the state transition table 60 and the resulting state transition diagram.
[0057] Reference now Fig. 9 , the method 100 of the present disclosure is shown in simplified form as being organized into discrete logic blocks. Each logic block further represents a process to be performed by the method 100 when executing the method 100. Figure 1 The specific process steps, functions or sub-processes performed by the host computer 12 are described in detail below. That is, the memory 54 of the host computer 12 is programmed with or otherwise includes a set of instructions executable by the processor(s) 53. As described above, the host computer 12 may be embodied as a plurality of digital computer systems or processing nodes, such as, Figure 1A , 12N, for example, as part of a distributed computing network, or the host computer 12 may be a stand-alone device such as a laptop or user workstation. Fig. 9 The constituent logic blocks of may be implemented as machine-readable codes executed by host computer 12 or one or more processing nodes 12A, 12B, . . . , 12N without limitation.
[0058] Starting from block B102 ("REC(15)"), method 100 needs to start from Figure 1 The user 11 is shown receiving system characteristics 15. The system characteristics 15 may include user-defined states of the modeled system, as well as various state transitions, triggering events, and possibly other characteristics. Block B102 may include presenting a menu of possible states and events via the display screen 14, for example, by displaying the menu as an intuitive drop-down list, Figure 1 The display screen 14 and / or the host computer 12 are configured to receive touch and / or keyboard input from the user 11, such input indicating these system characteristics. The host computer 12 can then use the touch or keyboard input to determine the system characteristics 15, such as by reading the user entry or selection from a drop-down list.
[0059] Depending on the application, receiving system features 15 may require receiving user-initiated events, automatically occurring events, external or environmental events, and fault-triggered events of the modeled system. When the modeled system is a motor vehicle with automated driving system capabilities, non-limiting exemplary user-initiated events may include, for example, throttle and brake pedal position / force, steering input, HMI button or knob status, etc. Automatically occurring events may include timers, sensors, fault triggers, and external / environmental events may include roads, weather, etc.
[0060] Therefore, at block B102, Figure 1 The user 11 of the system assigns event rule states, upgrades or transitions between different states, categories (e.g., line weights, styles, and colors for building corresponding state transition diagrams), etc. The defined states and events / inputs are used to create an empty state table, and the user 11 will eventually select a state using a drop-down list or menu. After the host computer 12 receives the system feature 15, the method 100 proceeds to block B104.
[0061] Block B104 ("GEN STT i ”) includes generating in response to receiving system feature 15 Figure 1 The initial state transition table 19 of block B104 may be missing. Figure 7 Some or all of the assigned states of the illustrated exemplary state transition table 60, ie, the initial state transition table 19 is substantially blank, awaiting further data entry by the user 11. The method 100 then proceeds to block B106.
[0062] In block B106 (“GEN STT P ”), the method 100 includes filling the initial state transition table 19. This action is responsive to Figure 1 The process occurs based on a set of user inputs 16 and includes automatically generating a populated state transition table 20 by the host computer 12. Here, the user inputs 16 are used to fill in the various states of the state transition diagram 19, thereby creating a more similar Figure 7 The output of the state transition diagram 60. Once the host computer 12 successfully automatically generates the populated state transition table 20, the method 100 proceeds to block B108.
[0063] As part of block B106 or in a subsequent step, method 100 may include receiving, via host computer 12, one or more meaning containers ("containers") in which two or more assigned states are grouped together, and also converting such user-assigned containers into corresponding state hierarchies. As described above, this action may require displaying to user 11 via display screen 14 Figure 5 The intuitive drag-and-drop graphic 56 of FIG. 1 and thereafter receives the container as a user response to the drag-and-drop graphic 56. The host computer 12 may then use, for example, Figure 1 The host computer 12 may transmit a validity confirmation status signal to the user 11 in response to confirming the validity of the state transition of each event type, for example, as a Figure 1 Warning signal (CC 22 ). The method 100 then proceeds to block B108.
[0064] In block B108 (“T CRIT =T? "), the host computer 12 then performs an error checking routine on the populated state transition table 20. This action uses the error checking routine recorded in the memory 54 and can be used by the ECM 52 ( Figure 1 ) access occurs, and may include searching the populated state transition table 20 for the missing transition. Events, super events, and states defined in the modeled system will appear in the transition table 20. If the transition is not filled after the state transition table is filled, the transition is considered missing within the scope of block B108. In addition, certain errors may be identified based on the identity of the container or the state and event criticality. As described above, the missing key transitions may be highlighted in the populated state transition table 20 to guide the user 11 to further consider. For example, the host computer 12 may create a color-coded background, outline, or text color for some transitions in the populated state transition table 20 to attract the user's attention to such transitions. As the host computer 12 makes all possible combinations of states and events explicit, the user 11 must fill in each cell to prevent inadvertently missing transitions. Thereafter, when the host computer 12 positively detects the missing transition, the method 100 proceeds to block B109, and when the host computer 12 does not detect the missing transition, the method 100 proceeds to block B112.
[0065] Block B109 ("ALRT") includes transmitting an alert to user 11 in response to a missed transition. For example, host computer 12 may Figure 1A visual alert message or graphic is displayed on the display screen 14 of the system, thereby giving the user 11 an immediate visual indication of the key features that are missing. In some implementations, the alert may be enhanced by auditory or tactile feedback. The graphic may include a highlighted portion of the populated state transition table 20 to draw the user's attention to the missing features, some of which may be functionally critical features and therefore important to design into the FSM of the system being modeled, as described above. The method 100 then proceeds to block B110.
[0066] In block B110 ("UPDT(16)"), Figure 1 The host computer 12 shown in FIG. 1 can receive updated user input 16 from the user 11 to fill in the populated state transition table 20, thereby generating an updated version of the populated state transition table 20. In this block or one of the previously described blocks, the host computer 12 can receive one or more user-defined composite events that are a combination of the events described above, and then update the populated state transition table 20 with the user-defined composite events.
[0067] Block B110 may optionally include receiving a customized event query from user 11 via host computer 12, as described above with reference to Figure 8 As described above, the customized event query describes one or more hypothetical combinations of events. In response to receiving such a query, the host computer 12 can determine the result of the event query and update the populated state transition table 20 with the result. Thereafter, the method 100 returns to the above-mentioned block B106. Therefore, blocks B102 to B110 are intended to be iterative here, prompting the user 11 to refine the populated state transition table 20 through multiple iterations. This occurs until the user 11 is satisfied with the completeness and accuracy of the populated state transition table 20, or until Figure 1 The host computer 12 no longer detects errors or omissions in the populated state transition table 20.
[0068] Block B112 ("GEN STT F ”) including the generation of Figure 1 The final state transition table 21 of the method 100 is provided as an output file. The final state transition table 21 in the best implementation of the method 100 will include every possible state, state transition and event / event combination of the modeled system, and will also include functionally critical states associated with the specific modeled system. Continuing with the above non-limiting motor vehicle example, for example, the main computer 12 and the execution of the method 100 will ensure that automated driver protection systems, stability, traction, steering, braking, lane keeping and other possible automated driver assistance functions are fully considered when developing HMI software for use by operators of such motor vehicles.
[0069] Although it is conceivable that for complex modeled systems, some non-critical functions may be omitted, the present method should fully capture the critical functional behaviors of the modeled system. In this way, the final state transition table 21 is ready for development of an actual production-ready system. As will be appreciated by those skilled in the art, a complete, error-tested version of the final state transition table 21 can be used to develop corresponding state transition diagrams and underlying computer code, such as programming an HMI device or control system to perform various actions in response to a dynamically changing environment. Likewise, it is unlikely that an actual system will enter an undefined state or terminal state with no exit, or a race or competition condition that results in a state transition that can change in an unpredictable manner.
[0070] Therefore, the solution of the present disclosure is to Figure 1 The user 11 is provided with an improved data entry method that facilitates the design of complex systems and the construction of decision trees. Functionally critical systems, in particular, are often composed of extremely complex behaviors in view of their numerous states, conditions, alarms, warnings, conditionals, and escalation protocols. Using the host computer 12 and its programming functions as described above, the user 11 is intuitively guided through automated emphasis on critical states and events. The user 11 is also encouraged to explore functionally critical combinations of events (super events) while highlighting possible errors. If a critical state or event is missing, the host computer 12 is configured to alert the user 11 to this fact, thereby prompting further iterations of the method 100. In view of the present disclosure, those skilled in the art will understand these and other attendant benefits.
[0071] For the purposes of this description, unless otherwise stated, the use of the singular includes the plural and vice versa, the terms "and" and "or" shall be both conjunctions and disjunctions, and the words "include", "comprise", "includes", "have", etc. shall mean "including but not limited to". In addition, approximate words such as "about", "almost", "substantially", "roughly", "approximately", etc. may be used herein to mean "at, around, or close to" or "within 0 to 5% of" or "within acceptable manufacturing tolerances" or their logical combinations. As used herein, a component "configured to" perform a specified function is capable of performing the specified function without modification, not merely having the potential to perform the specified function after further modification. In other words, the described hardware, when explicitly configured to perform a specified function, is specifically selected, created, implemented, utilized, programmed and / or designed for the purpose of performing the specified function.
[0072] The detailed description and the accompanying drawings or figures support and describe the present teaching, but the scope of the present teaching is limited only by the claims. Although some best modes and other embodiments for implementing the present teaching are described in detail, there are various alternative designs and embodiments for practicing the present teaching defined in the appended claims. In addition, the present disclosure explicitly includes combinations and sub-combinations of the elements and features presented above and below.
Claims
1. A method for generating a populated state transition table for a modeled system, comprising: receiving system characteristics from a user via a host computer, wherein the system characteristics include states, state transitions, and events of the modeled system; generating an initial state transition table in response to receiving the system characteristic, the initial state transition table being partially populated by the system characteristic; populating the initial state transition table by the host computer in response to a set of user inputs from a user of the host computer, thereby automatically generating the populated state transition table; error checking the populated state transition table using predetermined error checking criteria, including searching the populated state transition table for missing key features of the modeled system by error checking logic of the host computer; and An alert is transmitted to a user of the host computer in response to the missing critical feature.
2. The method according to claim 1, wherein: Receiving the system characteristics includes receiving user-initiated events, system-triggered events, and timeout events of the modeled system.
3. The method according to claim 1, further comprising: iteratively performing the method until the host computer does not detect the missing key feature; as well as Once the host computer does not detect the missing key feature, the populated state transition table is output as a final state transition table.
4. The method according to claim 1, further comprising: presenting a menu of possible states and events of the modeled system to a user via a display screen of the host computer; as well as The system characteristics are determined by the host computer using touch or keyboard input.
5. The method according to claim 4, further comprising: The menu is displayed as a drop-down list, wherein receiving the system feature includes recording a user entry or selection from the drop-down list.
6. The method according to claim 1, further comprising: receiving, by the host computer, one or more meaning containers in which two or more of the states are grouped together; as well as Transform the meaning container into a state hierarchy.
7. The method according to claim 6, further comprising: presenting intuitive drag-and-drop graphics or editing tools to a user via a display screen of said host computer; as well as The one or more meaning containers are received as a user response to a drag-and-drop graphic or editing input from the editing tool.
8. The method according to claim 6, further comprising: confirming, by the host computer, the validity of the state transition of each event type in each corresponding meaning container in the meaning container; as well as A validity confirmation status is communicated to the user in response to confirming the validity of the state transition for each event type.
9. The method according to claim 1, further comprising: receiving a user-defined composite event that is a combination of said events; as well as The populated state transition table is updated with the user-defined composite event.
10. The method according to claim 1, further comprising: receiving, by the host computer, a customized event query from a user, the customized event query describing one or more hypothetical combinations of the events; Determining, by the host computer, a result of the event query; as well as The populated state transition table is updated with the result.
