Systems and Methods for a Control System for a Vehicle

The control system for a vehicle includes processing circuit, and memory and a touchscreen. The processing circuit detects the characteristics of contact (e.g., touch) between the user's hand and/or an object and the touch-sensitive surface of the touchscreen. Responsive to the touch, the control system may present touch controls of a particular class on the touchscreen, establish sub-areas of the touchscreen, and/or control the operation of a system of the vehicle. The touch controls displayed on the touchscreen may perform the function of a dynamic touch control in that the graphic of the icon of the touch control may change to provide status regarding the operation of the system related to the touch control.

BACKGROUND

Embodiments of the present invention relate to a control system for a vehicle.

Vehicle drivers would benefit from control system that includes a touch-sensitive surface for displaying touch controls (e.g., icons) in accordance with frequency of use (e.g., often, regularly, rarely) and the position of the user in the vehicle (e.g., driver side, passenger side). Further, benefit may be accrued by presenting information in accordance with the type of gesture (e.g., touch) used by the user to touch the touchscreen of the control panel.

SUMMARY

An example embodiment of the control system according to the present disclosure includes a touchscreen with a touch-sensitive surface that displays touch controls (e.g., icons) for selection by a user (e.g., driver, passenger). In an example embodiment, the touchscreen is positioned between the driver and the passenger to provide access to the touchscreen and the touch controls thereof by both the driver and the passenger. The touch controls displayed on the touch-sensitive surface may be manipulated by the user to control the systems of the vehicle.

The driver and/or the passenger May provide input (e.g., contact, gestures, swipes, touch) to the control system via the touch-sensitive surface of the touchscreen. Input may include taps, presses, long press, short swipes (e.g., strokes, touches), long swipes and so forth. Input by the user may be referred to in general as touch as in touching the touchscreen either manually or with an object. The user may touch the touch-sensitive surface of the touchscreen at any initial location, for any duration of time, in any direction (e.g., left, right, up, down, diagonally) of movement, at any speed of movement, along any distance of movement and cease contact at any last location of contact. One touch may be distinguished from another touch by differences in initial location of contact, duration of time, direction, speed, distance and/or last location of contact, which comprise the characteristics of the touch.

Touches of different types, meaning touches having different characteristics as described above, may be used to request that the control system present icons that are used often, regularly, rarely or never and/or icons of a particular class (e.g., control, system, driver, passenger). Further, a touch having specific characteristics may result in displaying touch controls useful only to the driver (e.g., driver class), touch controls useful only to the passenger (e.g., passenger class), or the icons of a particular class of icons.

While an icon is presented on the touch-sensitive surface of the touchscreen, the icon and the touchscreen cooperate with each other to enable the user to select the icon to perform a function by one or more vehicle systems. An icon displayed on the touch-sensitive surface of the touchscreen is referred to as a touch control. The touch control may identify the function of a vehicle system that will be controlled. After selection, the image of a touch control may change to present information regarding the function of the vehicle system related to the touch control. A touch control whose image changes to provide information to a user is referred to herein as a dynamic touch control or a dynamic icon. A dynamic touch control may present information regarding the status of the operation of a vehicle system.

DETAILED DESCRIPTION

Overview

Vehicle100, includes steering wheel110, rear-view mirror140, brake pedal160, accelerator pedal150and glovebox130. Touchscreen120/320is positioned between the steering wheel110and the glovebox130. The touch-sensitive surface122is accessible to the driver and/or the passenger. The touchscreen120/320provides an interface for the user (e.g., driver, passenger) to provide input to the control system200/300and to receive information from the control system200/300. Input from the user to the control system200/300enables the user to control the operation of the various systems of the vehicle100. Vehicle100may include an electric vehicle. Information from the control system200/300provides information to the user regarding the operation of the various systems of the vehicle100.

The touch-sensitive surface122displays information and detects touches by a user. The touchscreen120/320may present an icon (e.g., image, graphic, glyph,1920,1930,1940,1950,2130,2140,2150,2230,2232) on a specific portion of the touch-sensitive surface122. An icon present information to the user that has a meaning in the context of the control system. Generally, the information presented by an icon is related to the operation of a vehicle system. The information presented by an icon may identify a function that may be performed by the vehicle system.

While the icon is presented on the touchscreen120/320, the icon and the touch-sensitive surface122cooperate to form a touch control which may be manually operated by a user for controlling the function indicated by the icon. When the user touches a touch control, either manually (e.g., finger2020) or using an object (e.g., stylus), the touch-sensitive surface122detects the touch and the characteristics (e.g., initial location, duration, direction, speed, distance, last location) of the touch. The touch is correlated to the icon and thereby to the function of the vehicle system represented by the icon. Touching the touch control controls the operation of the function indicated by the icon. The touch controls provide the interface for the user to control the functions of the vehicle.

Icons displayed on the touch-sensitive surface122to form touch controls may be grouped into classes of icons. An icon class may include icons that relate to a specific vehicle system or function of the control system. For example, touch controls1920,1930,1940and1950belong to startup class1910which are displayed on the touch-sensitive surface122when the control system is initiated. The control system200/300may be programmed, including by a user, so that any icon may belong to the startup class1910. Other icon classes include, for example, wiper class2160, regeneration class2162, ride control class2164, and light class2166. A class of icons may relate to a specific user of the vehicle100(e.g., driver, passenger).

Icons may also be grouped (e.g., classified) into classes related to the frequency of use of the icon. Classes of icons related to frequency may include an often-used class, a regularly-use class, a rarely-used class and a never-used class. In an example embodiment, a specific touch type respectively is used to instruct the control system200/300to display a specific class of icons.

The touch-sensitive surface122may be divided into sub-areas (e.g.,1420,1430,1960) for presentation of touch controls. In an example embodiment, a specific type of touch is used to instruct the control system200/300to establish or eliminate sub-areas. In another example embodiment, a specific type of touch is used to instruct control system200/300to establish a sub area and to display a specific class of icons in the sub-area.

Further, the graphics (e.g., icon) of a touch control may be used to provide information to user regarding the status of the operation of the function represented by the touch control. For example, once the touch control for cellular communication is activated, the graphics of the touch control may be altered to provide information regarding the duration of the cellular call.

Touch Type

A user may touch the touch-sensitive surface122of the touchscreen120/320to provide information to the control system200/300. There may be a variety of touch types as distinguished by the characteristics of the touch. As discussed above, the characteristics of a touch may include an initial location of contact of the touch on the touch-sensitive surface122, the duration of the touch on the touch-sensitive surface122, the direction of movement of the touch along (e.g., against) the touch-sensitive surface122, the speed of movement of the touch along the touch-sensitive surface122, the distance of movement of the touch along the touch-sensitive surface122and the last location of contact of the touch on the touch-sensitive surface122.

Examples of some possible types of touches are shown inFIGS.5-11. The arrow510represents the path of movement of the finger of the user or an object (e.g., stylus, pen) from a position above (e.g., away from) the touch-sensitive surface122as it comes into contact with the touch-sensitive surface122. The area530(e.g., circle) represents the location of initial contact of the finger or object with the touch-sensitive surface122. The arrow520represents the path of movement of the finger or the object from a position of contact with the touch-sensitive surface122to a position out of contact (e.g., above, away from) with the touch-sensitive surface122.

The touch type illustrated inFIG.5, may be referred to as a short touch (e.g., tap), a medium touch, or a long touch depending on the duration of contact of the finger or object with the touch-sensitive surface122. In this touch type, the finger or object comes into contact with the touch-sensitive surface122along the path510, initially contacts the touch-sensitive surface122at area530, remains in contact with the touch-sensitive surface122in the area530for a period of time, and moves along the path520to cease contacting the touch-sensitive surface122.

In this touch type, the initial location of contact is substantially the same as the last location of contact. In other words, there is little or no direction of movement, speed of movement or distance of movement of the touch with respect to the touch-sensitive surface122. Duration of touch is used to distinguish between a short touch, a medium touch and a long touch. In an example embodiment, the duration of the short touch is between 100 milliseconds and 250 ms. The duration of the medium touch is between 300 ms and 500 ms. The duration of the long touch is greater than 800 ms.

The touch type illustrated inFIGS.6-8may be referred to as a swipe or a touch in a particular direction (e.g., up, down, right, left, diagonally). There are many different types of swipes because swipes may be characterized by the duration of the touch, the direction of movement of the touch, the speed of movement of the touch and the distance of movement of the touch. For example, as illustrated inFIG.6, the finger or object moves along path510to come into contact with the touch-sensitive surface122at the initial area of contact530. From the initial area of contact530, the finger or object moves in a direction, in this case rightward, away from the initial area of contact530for either a duration of time or a distance until the finger or object moves along path520to cease contacting the touch-sensitive surface122.

In an example embodiment, swipes or a touch in a particular direction may be characterized by the direction and distance the finger or object moves along the touch-sensitive surface122between the initial location in the last location. For example, a short touch in the upward direction (e.g., short-upward touch, short-upward swipe) is a touch that moves in the upward direction a distance of 0.5-1.5 inches. A medium touch in the leftward direction (e.g., medium-leftward touch, medium-leftward swipe) is a touch that moves in the leftward direction a distance of 2.5-3.5 inches. A long touch in the upper-right diagonal direction (e.g., long-upper-right touch/swipe, long-NE touch/swipe) is a touch that moves diagonally in a northeastern direction a distance greater than 5 inches.

In another example embodiment, the distance of a touch may be characterized as a portion of the width of the touch-sensitive surface122of the touchscreen120/320. For example, a short-downward touch is a touch that moves in the downward direction a distance of about ⅕ of the width of the touch-sensitive surface122. A medium-SW touch is a touch that moves in the southwestern direction a distance of about ⅖ of the width of the touch-sensitive surface122. A long-SE touch is a touch that moves in the southeastern direction a distance greater than or equal to ⅗ the width of the touch-sensitive surface122.

For example, referring toFIG.22, the touch1422, a short-rightward touch, begins at or near the left edge of the touch-sensitive surface122and ends approximately at the boundary of the sub-area1420. The distance between the left edge of the touch-sensitive surface122and the boundary of the sub-area1420is about ⅕ the width of the touch-sensitive surface122. The touch2322, the long-rightward touch shown inFIG.24, begins at or near the left edge of the touch-sensitive surface122and ends somewhere just past the middle of touch-sensitive surface122, which is a distance of about ⅗ of the width of the touch-sensitive surface122.

The directions illustrated inFIG.7identify the directions of movement that may be used to characterize a touch. For example, from initial area of contact530, the finger or object may move in an upward direction710(e.g., North), in a rightward direction716(e.g., East), in a downward direction714(e.g., South), in a leftward direction712(e.g., West), in diagonal direction720(e.g., Northeast, upper-right), in diagonal direction726(e.g., Southeast, lower-right), in diagonal direction724(e.g., Southwest, lower-left), or in diagonal direction722(e.g., Northwest, upper-left). Since a short, medium or long touch may be taken in any direction, there are at least 24 different varieties of touches in a direction (e.g., swipes). For example, a medium touch in the diagonal direction720is shown inFIG.8.

The movement of a touch is not limited to movement in a single direction. An out and back touch (e.g., swipe) is shown inFIG.9. The finger or object comes into contact with the touch-sensitive surface122along path510and at area530. The finger or object, while in contact with the touch-sensitive surface122, moves in an initial direction (e.g., up), momentarily stops moving but remains in contact with the touch-sensitive surface122, moves in the direction opposite the initial direction until it approximately reaches the initial area of contact530, then follows path520to cease contact with the touch-sensitive surface122. Because the initial direction may be any direction shown inFIG.7, there are at least eight different versions of the out and back touch (e.g., up-down, down-up, right-left, left-right, NE-SW, SW-NE, NW-SE, SE-NW). This type of touch may also be characterized by the distance of movement to create additional versions (e.g., short, medium, long) of the out and back swipe.

An out-back-out touch (e.g., swipe) type is illustrated inFIG.10A. The finger or object comes into initial contact with the touch-sensitive surface122along path510and at area530. The finger or object, while maintaining contact with the touch-sensitive surface122, moves in an initial direction (e.g., up), momentarily stops moving but remains in contact with the touch-sensitive surface122, moves in the direction opposite the initial direction (e.g., down) until it approximately reaches the initial area of contact530, momentarily stops but remains in contact with the touch-sensitive surface122, again moves in the initial direction (e.g., up), then follows path520to cease contact with the touch-sensitive surface122. Variations of initial direction, speed of movement and/or distance of movement may be used to create many different varieties out-back-out touches.

A 90-degree touch type is illustrated inFIG.10B. The initial direction of movement is in any direction, but the second direction of movement is in a direction that is at an angle of about 90 degrees with respect to the initial direction of movement. The directions of movement, the distance of movement, the speed of movement may be used to distinguish between a variety of 90-degree touches. The 90-degree touch1010, shown inFIG.10B, has the shape of the letter V while the 90-degree touch1020has the shape of a chevron. Touches may also approximate other letters of the alphabet. A touch that approximates the letter P is shown inFIG.11.

Each time the finger of the user or an object contacts the touch-sensitive surface122, the touch may be characterized as described above and identified as being a particular touch type (e.g., short touch, medium touch, long touch, short-rightward touch, long-rightward touch, up-down touch, so forth). The control system200/300may take an action in accordance with a specific touch type.

In an example embodiment, touch1422, which is a short-rightward touch, as best seen inFIGS.14and22, instructs the control system200/300to establish sub-area1420on touch-sensitive surface122and to display the driver class icons2210in sub-area1420. Touch1432, a short-leftward touch best seen inFIGS.14and23, instructs the control system200/300to establish sub-area1430on touch-sensitive surface122and to display the passenger class icons2310in sub-area1430. The sub-areas1420and1430may be established at any time by the user performing the touch1422and the touch1432respectively. The user may program the icons that belong to the driver class icons2210or the passenger class icons2310.

The touch controls and/or information displayed on the touch-sensitive surface122in the area that is not sub-area1420and/or1430is not affected by the touch1422and/or touch1432but remains the same as that which was being displayed before the touch1422or1432occurred. For example, referring toFIG.22, the touch1422establishes the sub-area1420on the left-hand portion of the touch-sensitive surface122and the driver class icons2210cover the sub-area1420; however, the information and touch controls displayed on the remainder of the screen, sub-area1960, remains unchanged.

Touch1412, best seen inFIGS.14and20, is a long-downward touch. Touch1412instructs the control system200/300to eliminate sub-areas1420and1430on the touch-sensitive surface122, if they exist, and to display one or more classes of icons on the full area2110of the touch-sensitive surface122. For example,FIGS.20-21show that touch1412eliminates the sub-area1420to display the wiper2160, regeneration2162, ride control2164and light2166icon classes on the full area2110(e.g., full-screen area) of the touch-sensitive surface122.

Touch Control

As discussed above, an icon cooperates with the touch-sensitive surface122to form a touch control. Just as an icon may be associated with a function of a vehicle system, a touch control may be used to activate or deactivate the operation of the function of the vehicle system.

In an example embodiment, the icon1200is a graphic symbol that includes area1210and area1220. The area1210includes the word OFF while the area1220includes the word ON. The icon1200indicates that some type of an operation of a vehicle system may be turned on or off.

When icon1200is displayed on the touch-sensitive surface122, it becomes touch control1300. The control system200/300knows where the icon1200is located on the touch-sensitive surface122and can detect when the icon is touched. The control system200/300can interpret a touch on a touch control to initiate, terminate, or adjust the operation of a vehicle system. In this example, when the icon1200is displayed on the touch-sensitive surface122, it is identified by the control system200/300as being the touch control1300that controls whether the front defroster of the vehicle100is on or off. The user may touch area1210or area1222of the touch control1300to either turn the defroster off or to turn the defroster on respectively.

In an example embodiment, a short touch in the area1210is used to turn the defroster off. The characteristics of a short touch are illustrated inFIG.5and discussed above. The control system200/300detects the short touch in the area1210and construes the touch with the information provided by the icon1200to know that the touch control to turn the front defroster off has been activated.

In another example embodiment, best seen inFIG.13, icon1310, a rectangle oriented horizontally, is displayed on the touch-sensitive surface122to form the touch control1320to control the speed of a fan. In this embodiment, a medium-rightward touch is used to adjust the fan speed from off (e.g., speed 0) to speed 6. The control system200/300detects that the area of initial contact530coincides with the icon1310and that the touch is in the rightward direction along the icon1310. So, the icon1310in cooperation with the touch-sensitive surface122forms the touch control1320that is used to control the speed of the fan.

Touch controls may be displayed as images of buttons, sliders and/or checkboxes (e.g., radio button). Touch controls presented as buttons or checkboxes generally may be operated using a short touch, a medium touch or a long touch. Touch controls that are presented as sliders generally may be operated using a touch of a length and a direction that corresponds to the orientation of the slider. For example, a slider displayed horizontally on the touch-sensitive surface122maybe operated using a short, medium, or long touch (e.g., swipe) in the rightward or the leftward direction as best shown inFIG.13. A slider displayed vertically on the touch-sensitive surface122may be operated using touch (e.g., swipe) in the upward or downward direction.

Sub-Areas of the Touch-Sensitive Surface

As briefly discussed above, the touch-sensitive surface122of the touchscreen120/320may be subdivided into different sub-areas. Icons of different classes may be displayed in the various sub-areas. The control system200/300may recognize specific touch types as establishing or eliminating one or more sub-areas.

As discussed above, the touch1422instructs the control system200/300to establish the sub-area1420. As further discussed above with respect to touch types, touch1422starts as the finger or object approaches the touch-sensitive surface122along path510. The finger or object touches the touch-sensitive surface122at the initial location of contact530as best seen inFIG.14. The finger object moves in a rightward direction for a distance that defines the short touch1422, then the finger object lifts out of contact with the touch-sensitive surface122along path520. The touch1422may be performed at any location on the touch-sensitive surface122as long as the length requirement of the touch type is met. The control system200/300detects the touch type and establishes the sub-area1420. Icons may be displayed in the sub-area1420. The icons that were previously displayed on the touch-sensitive surface122outside of the sub-area1420may remain as previously displayed or they may be reorganized to fit on the area of the touch-sensitive surface122that excludes sub-area1420(e.g., sub-area1960).

In an example embodiment, the touch1432instructs the control system200/300to establish the sub-area1430. As discussed above with respect to touch types, touch1432starts with the finger or object approaching the touch-sensitive surface122along path510. The finger or object makes initial contact with the touch-sensitive surface122at location530. The finger or object moves leftward from the initial location of contact530for a distance that defines the touch1432, then the finger or object lifts from the touch-sensitive surface122along path520. The control system200/300detects the touch type and establishes the sub-area1430. The touch1432may be performed at any location on the touch-sensitive surface122as long as the length requirement of the touch type is met. Icons may be displayed in the sub-area1430. The icons that were previously displayed on the touch-sensitive surface122outside of the sub-area1430, and outside of the sub-area1420if established, may remain as previously displayed or they may be reorganized to fit on the area of the touch-sensitive surface122that excludes the sub-area1430and the sub-area1420if established.

As discussed above, in an example embodiment, the touch1422both establishes the sub-area1420and instructs the control system200/300to display driver class icons in the sub-area1420. In an example embodiment, the touch1432both establishes the sub-area1430and instructs the control system200/300to display passenger class icons in the sub-area1430.

In an example embodiment, touch1412eliminates sub-area1420and sub-area1430, if either or both are established, so that icons are displayed on the full area2110of the touch-sensitive surface122. The touch1412begins with the finger or object approaching the touch-sensitive surface122along path510. The finger or object makes initial contact with the touch-sensitive surface122at initial location530. The finger or object moves from the initial location of contact530in a downward direction a distance that defines the short touch1412, then the finger or object lifts from the touch-sensitive surface122along path520. The touch1412may be performed at any location on the touch-sensitive surface122as long as the length requirement of the touch type is met. Icons may be displayed in the full area2110. The icons that were displayed in the sub-areas1420and1430are no longer displayed on the touch-sensitive surface122. The icons that are displayed in the full area2110may include icons from one or more icon classes.

In another example embodiment, the touch2322in the rightward direction or the touch2232in the leftward direction may be used to sequentially display different classes of icons on the touch-sensitive surface122. In other words, the touch2322and the touch2332may be used to flip through pages of icons for the various vehicle systems. Referring toFIG.24, if either the sub-area1420or the sub-area1430or both are established, the icons will be displayed in the sub-area1960of the touch-sensitive surface122that does not include the sub-area1420, the sub-area1430or both. If sub-area1420and sub-area1430are not established, then successive pages of icons are displayed on the full area2110of the touch-sensitive surface122. The icons for one or more vehicle systems210(e.g., one or more icon classes) may be displayed on the touch-sensitive surface122at the same time.

Classes of Icons

Icons may be grouped together into classes. In an example embodiment, icons related to a single vehicle system are grouped together into a single class. For example, all icons used to control the operation of the HVAC system212are identified as being members of the HVAC class of icons. Each system, including the infotainment system214, the light system216, the suspension system218, the communication system220, the seats system222, the stability system224, and any other system of the vehicle100may have icons that may operate as touch controls to control the operation of the respective system. The icons for each system may belong to an icon class for that vehicle system. A vehicle system may have two or more classes of icons. The icons related to two or more vehicle systems may be part of the same icon class. Preferably, a user may program (e.g., specify) the icons that are a part of a class or even defined new classes of icons.

In another example embodiment, icons are grouped into classes that are related to the frequency of use of the icons. In this example embodiment, the icon classes include the often-used class, the regularly-used class, the rarely-used class and the never-used class. The definitions of often-used, regularly-used, rarely-used and never-used may include any amount of use during any duration of time. In an example embodiment, the user may set the definition of the amount of use per duration of time. In an example embodiment, often-used icons include those icons that are used at least five times per week. Regularly-used icons include those icons that are used at regular intervals regardless of the length of the interval. Rarely-used icons include those icons that are used at most once every six months. Never-used icons include those icons that have not been used since the manufacture of the vehicle100or the last servicing of the vehicle100.

In another embodiment, the often-used icon class include those icons that are displayed on the touch-sensitive surface122of the touchscreen120/320and used as a touch control two or more times per week. The regularly-used icon class includes icons that are displayed on the touch-sensitive surface122of the touchscreen120/320and used as a touch control less than two or more times per week, but at least one time per month. The rarely-used icon class includes icons that are displayed on the touch-sensitive surface122of the touchscreen120/320and used as a touch control less than one time per month, but at least one time per six months.

Specific touch types may be used to instruct the control system200/300to display a specific class of frequency-based icons. In an example embodiment, a first long-downward touch instructs the control system200/300to display the icons of the often-used icon class. A second long-downward touch instructs control system200/300to display the icons of the regularly-used icon class. A third long-downward touch instructs control system200/300to display the icons of the rarely-used icon class. A fourth long-downward touch instructs control system200/300to display the icons of the never-used icon class. If any class of the frequency classes of icons cannot be displayed in a single full screen2110, touch2322and/or touch2332may be used to page through the additional pages of the class.

In another example embodiment, the various classes of frequency-based icons may be displayed using any four different touch types. For example, touch1010, touch1020, touch820and touch920. In another example embodiment, different versions of the 90-degree touch may be used to display the various classes of the frequency-based icons.

Control Systems

As discussed above, the user may provide input to the control system200/300via the touch-sensitive surface122to control the various systems of the vehicle100. In a first example embodiment, the control system200includes a processing circuit250, a memory260, vehicle systems210, a touchscreen120, and a bus290. The control system200may further include a haptic pad112and/or a haptic pad114. The touchscreen120of the first example embodiment includes a touch-sensitive surface122, a display controller270, a processing circuit272, a memory274and a touch identifier280. The bus290enables the components of the first embodiment of the control system200to communicate with each other.

The vehicle systems210include the systems of the vehicle100that operate to enable the vehicle100to perform the functions of the vehicle. In an example embodiment, vehicle systems210includes HVAC system212, infotainment system214, lights system216, suspension system218, communication system220, seat system222, stability system224and any other system that is used to perform a function of the vehicle100. The list of vehicle systems given herein does not include all systems that may be a part of vehicle100.

In the first embodiment, control system200, the processing circuit272, the memory274and the touch identifier280detect contact of a finger or an object with the touch-sensitive surface122of the touchscreen120, identify the touch type (e.g., short touch, short-leftward, so forth), identify any touch control that is been touched, identify the vehicle system associated with any touch control that has been touched, and report the information that has determined to the processing circuit250. The processing circuit250, responsive to the information from the touchscreen120, controls the vehicle system related to touch control that was touched. The processing circuit250may also provide status of the vehicle system to the touchscreen120. The touchscreen120may use status information from the processing circuit250to provide status information to user via a dynamic touch control displayed on the touch-sensitive surface122.

The touchscreen120of the first embodiment includes sufficient processing power and data to perform most of the functions related to the touchscreen120, identifying touch types, displaying icon classes, detecting operation of touch controls, managing dynamic touch controls and reporting the operation of a touch control while the processing circuit250controls and monitors the vehicle systems210in accordance with the information regarding touch controls from the touchscreen120.

In a second example embodiment, the control system300includes the processing circuit250, the memory260, the vehicle systems210, touchscreen320and the bus290. The touchscreen320of the second example embodiment includes the touch-sensitive surface122and the display controller270. The control system300may further include the haptic pad112and/or the haptic pad114. The bus290enables the components of the second embodiment of the control system300to communicate with each other.

The processing circuit250controls and monitors the vehicle systems210in addition to controlling and operating the touchscreen320. Processing circuit250provides information, such as icons, to the touchscreen320for display on the touch-sensitive surface122. The display controller270manages the display of objects on the touch-sensitive surface122. The touchscreen320reports the initial location, duration, distance, direction, speed and last location of any touch on the touch-sensitive surface122. The processing circuit250determines the touch type, any icons that may have been touched, any touch controls that may have been operated, any system related to the touch controls, and the function of the system affected by the touch controls. Processing circuit250controls and manages the vehicle systems210and provides status information regarding the vehicle systems to the touchscreen320for display on the touch-sensitive surface122via dynamic touch controls.

In either embodiment of the control system, haptic pads112and114may detect touch information. Because icons cannot be displayed on the haptic pad112or114, the touch information received via the haptic pad112or114may be related to touch types that instruct the control system200/300to take a specific action. As discussed above, specific actions may include establishing or eliminating a sub-area and/or displaying a specific class of icons.

In an example embodiment, a short-rightward touch (e.g.,1422) on haptic pad112or114instructs the control system200/300to establish the sub-area1420. In another example embodiment, the short-rightward touch on haptic pad112or114instructs the control system200/300to establish the sub-area1420into display the passenger class icons2210in the sub-area1420.

In another example, a long-leftward or long-rightward touch (e.g.,2332,2322on haptic pad112or114would instruct the control system200/300to successively display icon classes on the touch-sensitive surface122. For example, assume that the dashboard class2320icons are displayed in sub-area1960. Touch2322or touch2332on the haptic pad112or114may be used to show the next class of icons in sub-area1960. In an example embodiment, touch2322may be used scroll from the dashboard class2320icons, as shown inFIG.23, to the HVAC class icons2420as shown inFIG.24. A further touch2322scrolls to the information class icons2240and so forth to page through all icon classes.

The control system200/300may further include mechanical buttons, not shown, or other types of conventional switches (e.g., switches, sliders) for manual operation by a user to provide information to the processing circuit250. The buttons may be used to control a function of the vehicle. In an example embodiment, the vehicle100has a mechanical button for starting the vehicle. The buttons may cooperate with the touchscreen120/320to activate or deactivate a function of the vehicle. The buttons may cooperate with the touchscreen120/320and/or touch controls displayed on the touch-sensitive surface122to provide information regarding performance of a function of the vehicle. One or more mechanical buttons may exclusively control a function of the vehicle, such that the function is not controlled via a touch control presented on the touch-sensitive surface122. In an example embodiment, activating or deactivating the emergency flashers is exclusively controlled by a mechanical button.

Memory

A memory (e.g.,260,274) may store information for use by a processing circuit (e.g.,250,272) to store icons for vehicle systems, to identify icon classes, to identify icon classes based on frequency, to establish or eliminate sub-areas on the touch-sensitive surface122, to identify touch types and to map icons for display in the areas of the touch-sensitive surface122.

In an example embodiment, the memory (e.g.,260,274) includes some or all of the data400best seen inFIG.4. Data400includes icon classes410. The data of icon classes410categorizes classes of icons with respect to vehicle systems. Icon classes410identifies the icons associated with each vehicle system of the vehicle100. The data of icon classes410may store the graphic information related to the icons for the vehicle systems including information for dynamic touch controls. For example, HVAC class412includes the information regarding all icons associated with the HVAC system212. Information may include the operation to be performed, modified, or ceased when the icon operates as a touch control in association with the touch-sensitive surface122. Infotainment class414, lights class416, suspension class418, communication class420, seat class422and stability class424include information related to the icons for the infotainment system214, the light system216, the suspension system218, the communication system220, the seat system222and the stability system224respectively.

Icons by frequency430groups icons from the various vehicle systems into the often-used, regularly-used, rarely-used and never-used icon classes. Often-used432stores information regarding the icons that are often presented on the touch-sensitive surface122and used as a touch control. Regularly-used434stores information regarding the icons that are regularly presented on the touch-sensitive surface122and used as a touch control. Rarely-used436stores information regarding the icons that are rarely presented on the touch-sensitive surface122and used as a touch control. Never-used438stores information regarding the icons that have never been presented on the touch-sensitive surface122and used as a touch control. The requirements for categorizing icons with respect to frequency of use are discussed above. Icons by frequency430may include some or all of the information from icon classes410but grouped and arranged by frequency of use.

Touchscreen areas440includes information regarding the sub-areas of the touch-sensitive surface122. Each area442,444,446,448,450and452may include information regarding the location and size of each sub-area. Touchscreen areas440may include information regarding the touch type needed to establish or eliminate a particular area. In the examples provided above, information for sub-area1440, sub-area1430and sub-area1960would be stored in area442, area444, and area452respectively. Area442may include information that sub-area1420is established by touch1422. Area444may include information that sub-area1430is established by touch1432. Touchscreen areas440may further include information for each area as to the icon class that should be displayed in the sub-area upon its creation.

Touch types460includes information for identifying each type of touch detected by the control system200/300. Each touch type462,468and so forth include the information needed to identify the touch type. For example, touch type462includes characteristics464that describes the duration, the direction of movement, the speed of movement and/or the distance of movement of a touch that qualifies to be identified as touch type462. Touch type468includes characteristics470that describes the duration, the direction of movement, the speed of movement and/or the distance of movement of a touch that qualifies to be identified as touch type468. Each touch type that is recognized by control system200/300is identified in touch types460.

Each touch type462,468and so forth further may further include information as to what action should be taken upon detecting the touch type. For example, in one embodiment, action466specifies that upon detecting touch type462(e.g., touch1422), the control system200/300should create the sub-area1420on the touch-sensitive surface122. In another embodiment, action466specifies that upon detecting touch type462(e.g., touch1422), the control system200/300should create the sub-area1420on the touch-sensitive surface122and present the driver class icons2210in the sub-area1420. If no action is to be taken based on touch type alone, action466and/or action472is omitted or left empty for a particular touch type.

Icon mapping480stores information as to the icons that should be displayed on the touch-sensitive surface122in a particular sub-area. For example, area482, area486and area490specify a specific sub-area, or full-area2110, of the touch-sensitive surface122. The icons identified in icons484, icons488and icons492should be displayed in the area482,486and490respectively. The information in icons484, icons488and icons492may include some or all of the information in icon classes410and/or icons by frequency430. The icons for area482,486and490may be changed and/or updated at any time to display any icon in any area when needed.

The data400is not limited to the examples of data identified herein. Data400may include any data needed to display icons, to detect touch types, to detect the operation of touch controls, to perform a function responsive to a touch control, and/or to control dynamic touch controls.

Dynamic Touch Controls

As discussed above, an icon, and thereby a touch control, may be static or dynamic. The image of a static touch control does not change. Whether touched or untouched, the image of a static touch control remains the same all the time. A static touch control does not provide status information regarding the function of the vehicle system associated with the static touch control. In an example embodiment, referring toFIG.21, touch control2140for the ride height of the vehicle100is a static touch control. If the user activates the up arrow of the touch control2140to increase the height of the ride, the image of the touch control2140does not change. The user can detect the change in the ride height through feeling movement of the vehicle100or visually.

Other touch controls may be dynamic. For example, referring toFIG.22, the touch controls2230and2232are dynamic touch controls that cooperate with each other. When the headlights are turned on and the high beams are enabled, the touch control2230is highlighted (e.g., lit, green color) to show that the high beams are enabled and the touch control2232is not highlighted. When touch control2232is touched to enable the low beams, the touch control2232is highlighted and the touch control2230changes so that it is no longer highlighted. Highlighting touch control2232shows that the low beams are enabled and removing the highlight from the touch control2230shows that the high beams are not enabled. Highlighting a touch control to show that the function related to the touch control is active is only one way of providing status information to a user.

In another example of a dynamic touch control, referring to image1500ofFIG.15, touch control1510may be used to control playback from the infotainment system214. The touch control1510may be touched the start playback of some type of media (e.g., radio, podcast, CD). The touch control1520may be touched to mute or unmute the speakers that are playing back the media. When touch control1510is touched with a short touch (seeFIG.5), the image1500changes to image1600, as best seen inFIG.16. In image1600, the touch control1510has changed from the play symbol to the pause symbol, so that playback of the media may be paused upon touching the touch control1630. Touch control1520remains the same to permit muting and unmuting of the speakers.

However, image1600is dynamic in that image1600provides information regarding the media being played. In this example, area1610of image1600provides the title of the song being played and the name of the group performing the song. Further, in area1620, information regarding the elapsed time of playback and the total time of the song is provided. So, image1500is a dynamic touch control that when activated changes to image1600to provide information regarding the status of playback.

In another example, referring toFIG.17, image1700includes touch control1710which activates cellular telephone communication via the hands-free system installed in the vehicle100. In this example, when an incoming phone call arrives, the communication system220notifies the user by causing a ringing sound. If the user desires to receive the incoming call, the user touches touch control1710to pick up the call. Upon touching touch control1710, the image1700changes to image1800.

The image1800not only provides information regarding the caller and the duration of the call in area1840, but also provides additional touch controls1810,1820and1830to provide further control over the communication system220. The touch control1810, when selected, terminates the phone call. When touch control1810is activated, the call is terminated and image1800is replaced with image1700.

The touch control1820enables the user to mute and unmute the microphone of the hands-free system while talking on the phone. The touch control1820may also be a dynamic touch control in that when the microphone is muted, touch control1820is highlighted. When the microphone is not muted, touch control1820is not highlighted. Touch control1830may be used to mute the speaker that enables the user to hear the caller. When the touch control1820or1830is activated, it is highlighted to show that muting is on. When touch control1820or1830is not active, it is not highlighted to show that muting is off.

The status information of the call that is shown in area1840of the image1800is displayed until the call is terminated by touching touch control1810. Additional call information that may be displayed in area1840may include cellular phone signal strength, cellular phone battery level and/or time of day.

As shown in these two examples, the image of a dynamic touch control is different before activation and after activation. The different images may be different in size and may require more or less area for display on the touch-sensitive surface122. For example, the area of the image1500on the touch-sensitive surface122is less than the area of the image1600. Further, the area of the image1700is less than the area of the image1800. The display of the touch controls on the touch-sensitive surface122may be adjusted as the area of the image of dynamic touch controls changes (e.g., increases, decreases).

The control system200/300may be, to some extent, programmable by a user. As discussed above, programmability may include identifying the criteria for categorizing touch controls as often-used, regularly-used or rarely-used. For example, a user may specify that often-used touch controls are used daily, regularly-used touch controls are used at least once a week and rarely-used touch controls are used at most once a month.

Programmability may further enable the user to organize icons into specific groups. For example, a user may specify the icons that are associated with the driver class icons and/or passenger class icons. Further, a user may specify that certain icons of a vehicle system class not be displayed because the user has no intention of using those icons as touch controls. Further, the user may specify specific icons as being part of the favorites class of icons. A user may further group icons according to different users of the vehicle100.

Another aspect of programmability may include allowing the user to specify the status information that is displayed by a dynamic touch control. For example, referring toFIG.18, a user may specify that the information displayed in area1840include the battery level of the cell phone. In another aspect, programmability may enable the user to select from a variety of images for a particular icon or touch control. The user may change the color and/or size of an icon.

In another aspect of programmability, the user may specify the size and placement of the sub-areas of the touch-sensitive surface122. Further, the user may specify the touch type that establishes or eliminates sub-areas. Further, the user may specify the touch type for any action that may be performed by the control system200/300. The user may specify the touch controls that are displayed when the control system200/300is initialized (e.g., startup class1910) at the starting of the vehicle100. The user may specify which touch controls appear together on a screen. Any aspect of the operation of the touch control system200/300may be programmable by a user especially with respect to how touch controls are displayed, the actions associated with a particular touch type or the content of an icon class.

In Operation

While the vehicle100is not in its operational mode (e.g., turned on, running) many if not most of the vehicle systems210are not operating and may even be powered down. Some vehicle systems are powered up and operational. For example, in an example embodiment, while the vehicle is not operational, the locking system, not shown, is active to receive signals from a remote controller (e.g., key FOB) to lock or unlock the doors. Processing circuit250and memory260may be in an operational state or in a low-power operational state to be able to control and/or monitor those vehicle systems that are enabled and powered up.

While the vehicle100is not in its operational mode, the touchscreen120/320is likely powered down or in a low power state. In the example embodiment, the touchscreen120/320is powered down and no information is displayed on the touch-sensitive surface122.

The vehicle100transitions from the non-operational mode to the operational mode in any manner. In an example embodiment, the locking system detects the proximity of the remote controller, and the user activates a mechanical button to cause the vehicle100to enter the operational mode. In another example embodiment, the locking system detects the insertion of a key into an ignition and as a result enters the operational mode. Upon entering the operational mode, the control system200/300is powered and fully enabled. In another example embodiment, while the vehicle100is in the non-operational mode, the touchscreen120/320is active and displays icon1920with lock touch control1922and unlock touch control1924so that the doors may be locked and unlocked without the vehicle100entering the operational mode.

In the example embodiment, upon entering the operational mode, as best shown inFIG.19, the control system200/300, enables the touchscreen120/320, establishes sub-area1420and displays the startup class1910of icons in the sub-area1420. The icons that belong to the startup class1910may be programmed by the user. In the example embodiment, the startup class1910includes a door lock touch control1920, a touch control1930for accessing the dashboard class2320icons, a touch control1940for accessing the infotainment class icons, and touch control1950for accessing a settings class icons. Touching (e.g., short touch) the touch control1922locks the doors of the vehicle100. Touching the touch control1924unlocks the doors of the vehicle100. Touching the touch control1930,1940or1950causes the control system200/300to display dashboard class2320icons, infotainment class icons (not shown) or settings class icons (not shown) respectively on the touch-sensitive surface122. The icons as displayed on the touch-sensitive surface122operate as touch controls related to the various classes of the vehicle systems. The icon classes may be presented in the sub-area1960or the sub-area1420may be eliminated and the icons displayed on the full-screen area2110.

In the example embodiment, instead of touching one of the touch controls1920-1950, referring toFIGS.20-21, the user may use touch2010, which is a long-downward touch, to instruct the control system200/300to display one or more icon classes on the full area2110. In the example embodiment, touch2010results in displaying the wiper2160, regeneration2162, ride control2164and light2166icon classes on the touch-sensitive surface122. The icon classes that are displayed may be programmed by the user. From the screen shown inFIG.21, the user may touch any of the displayed touch controls to control the system associated with the touch control. For example, the user could touch (e.g., short touch) touch control2130to activate/deactivate descent assist. The user could use touch control2150to activate/deactivate the light in the front trunk (e.g., frunk).

The user may also use the touch2322and/or the touch2332to page (e.g., flip, scroll) through the icon classes for the various vehicle systems and/or the icon classes based on frequency of use. For each use of the touch2322or2332, the control system200/300presents one or more different classes of icons on the touch-sensitive surface122. When the user has found the icon class of interest, the user may use the touch controls of that class to control the associated vehicle system. At any time, the user may use touch1422to create sub-area1420to display the driver class icons2210or touch1432to create sub-area1430to display the passenger class icons2310.

Another example class of icons that may be displayed, as best seen inFIG.22, is the information class2240icons. Many, if not all, of the icons of the information class2240provide information and thereby function as dynamic touch controls. For example, messages2242provide information as to the messages (e.g., text messages, voice) that have arrived via the communication system220. Touching any one of the message touch controls displays or plays the message. Schedule2244displays information regarding the user's schedule. Touching any one of the schedule items provides information regarding the item. Reminders2246may be touched to modify or deactivate the reminder. Weather2248may be touched to receive more detailed information with respect to the weather.

Not all icons displayed as part of the information class2240are dynamic touch controls, but rather dynamic icons. For example, vehicle status2250presents information regarding the status of the operation of the vehicle100but touching any the icons of vehicle status2250does not result in an action. In other words, vehicle status2250merely presents information, even though it is updated periodically, rather than functioning as a touch control. The user would need to navigate to the appropriate vehicle system page to modify the operation of the vehicle100. Further, the navigation status2252may be dynamic icons that provide information rather than dynamic touch controls.

Methods

An example embodiment of a method is shown inFIG.25. The example embodiment, the method2500, is performed by the control system200/300to perform the functions of the control system200/300. The processing circuit250may execute a stored program to perform the example embodiment method2500. The example embodiment method2500includes detect2510, identify2512, area2520, icon2522, activate2524, area2530, establish2532, display tray534, area2540, establish2542, display2544, class2550, display2552, class2560, display2562, identify2570, activate2572, dynamic2574and update2576.

Detect2510detects contact of a finger or an object with the touch-sensitive surface122of the touchscreen120/320. Detect2510detects the initial location of contact of the finger or object with the touch-sensitive surface122. Detect2510determines the duration of time of contact of the finger or object with the touch-sensitive surface122. Detect2510detects the direction of movement of the finger or object along the touch-sensitive surface122. Detect2510detects the speed of movement of the finger or object along the touch-sensitive surface122. Detect2510detects the distance of movement of the finger or object along the touch-sensitive surface122. Detective2510detects the last location of contact of the finger or object with the touch-sensitive surface122. Detect2510may record (e.g., save, store) the information detected. As discussed above, detect2510may be performed by processing circuit272and/or processing circuit250of the control system200or processing circuit250of the control system300. The touchscreen120/320may provide information for determining the above.

Detect2510may also detect whether the finger or object came into contact with a touch control. Detect2510may determine the specific touch control or touch controls contacted by the finger or object, the location of contact on the touch control and/or the area or portion of the touch control contacted by the finger or object. Detective2510may report the touch control contacted by the finger or object so that the control system200/300may determine whether the touch should result in control of a vehicle system. Although detect2510does not control activation/deactivation of the vehicle systems, it provides the information so that it may be determined whether a vehicle system should be activated, deactivated and/or adjusted (e.g., controlled).

Identify2512uses the information detected by detect2510to determine the touch type of the contact (e.g., touch) of the finger or object with the touch-sensitive surface122. As discussed above, touch identifier280of the control system200may determine the touch type. Processing circuit250of the control system300may determine the touch type. Touch identifier280may use information from the memory274to identify the touch type. The processing circuit250may use information from the memory260to identify the touch type. As further discussed above, touch types may include a plurality of touch types.

Area2520, icon2522and activate2524identify a specific touch type and take action responsive to a specific touch type. Area2520identifies one or more touch types used to establish a sub-area on the touch-sensitive surface122. For example, touch1422, a short-rightward touch, and touch1432, a short-leftward touch, establish sub-area1420and sub-area1430respectively. Touch2010, a long-downward touch, eliminates all sub-areas so information may be displayed on the full area2110. Each time area2520identifies the touch type as a touch that establishes an area on the touch-sensitive surface122, control moves to2530.

Icon2522identifies one or more touch types used to display an icon class. In an example embodiment, touch1110, which resembles the letter P, instructs the control system200/300to display the passenger class icons on the touch-sensitive surface122. In another example embodiment, the touch1010(e.g., letter V) and the touch1020(e.g., chevron symbol), instructs the control system200/300to display the driver class icons and the passenger class icons respectively. Each time icon2522identifies the touch type as a touch that displays a class of icons, control moves to2550.

Activate2524identifies one or more touch types used to activate/deactivate a touch control. For example, short touch550may be used activate a touch control. For example, a short touch on touch control1510will cause the infotainment system214to play media. A short touch on touch control1520will mute or unmute the speaker of the infotainment system214. In another example, a touch in a direction along a slider, for example, slider1310inFIG.13, may be used to control the slider. Each time activate2524identifies a touch type that may be used to activate/deactivate a touch control, control moves to2570.

Once area2520has identified a touch type that relates to establishing or eliminating a sub-area, the touch type must be further categorized to determine which sub-area should be established or eliminated. Area2530and area2540relate a specific touch type to a specific sub-area. Area2530represents identifying a first specific touch type. Area2540represents identifying an Nth specific touch type. There may be any number of area2530/2440steps for identifying any number of specific touches for establishing or eliminating any number of sub-areas.

Area2530determines whether the touch type identified in area2520is the specific touch type for establishing sub-area no.1. If the touch type is the specific touch type for establishing sub-area no.1, establish2532is executed to establish the sub-area no.1. After the sub-area no.1is established, display2534may be executed to display the icons of icon class no.1in sub-area no.1. Display2534is optional. If display2534is not included, execution moves from establish2532to detected2510. If display2534is included, execution moves from display2534to detect2510. If the touch type is not a specific touch type for establishing sub-area no.1, control moves to area2540.

Area2540determines whether the touch type is the specific touch type for establishing sub-area no. N. If the touch type is the specific touch type for establishing sub-area no. N, establish2542is executed to establish the sub area no. N. After the sub-area no. N is established, display2544may be executed to display the icons of icon class no. N in sub-area no. N. As discussed above with respect to display2534, display2544is optional.

In an example embodiment, touch1422, a short-rightward touch, indicates that sub-area1420should be created and that the driver class icons should be displayed in the sub-area1420. Area2530could recognize touch1422, establish2532would establish sub-area1420and display2534would display the driver class icons in the sub-area1420.

Blocks2530-2534and2540-2544do not show steps for eliminating one or more areas; however, execution of a block for eliminating one or more areas upon recognizing a specific touch type could be added.

Once icon2522identifies a touch type related to displaying icons of a particular class, the specific touch type must be identified to determine which class of icons should be displayed. Class2550and class2560identify specific touch types. Class2550determines whether the touch type identified in icon2522matches the specific touch type for displaying class no.1icons. Class2560determines whether the touch type matches the specific touch type for displaying class no. N icons. There may be any number of steps similar to class2550or class2560for identifying any number of specific touch types related to displaying a specific class of icons.

Once class2550has determined that the touch type identified by icon2522is the specific touch type for displaying the icons of icon class no.1, execution moves to display2552which displays the icons of icon class no.1on the touch-sensitive surface122. If class2550determines that the touch type identified by icon2522is not the specific touch type for displaying the icons of icon class no.1, execution moves to class2560for further testing of the touch type.

If class2560determines that the touch type identified by icon2522is the specific touch type to display the icons of icon class no. N, execution moves to display2562which displays the icons of icon class no. N on the touch-sensitive surface122. If class2560determines that the touch type is not the specific touch type to display the icons of icon class no. N, execution moves to detected2510.

There may be as many class2550or class2560blocks as needed to identify all of the touch types that should result in the displaying the icons of a class. For example, class2550may identify touch1110(seeFIG.11) while class2560may identify touch1010(seeFIG.10B), and another class block may identify touch1020(seeFIG.10B).

Once activate2524detects a touch type used to activate/deactivate a touch control, identify2570is used to determine the touch control that has been touched. As discussed above, detect2510may determine which touch control displayed on touch-sensitive surface122was contacted by the finger or object. This information may be reported to identify2570. Knowing which touch control was touched may include such information as the vehicle system related to the touch control, the operation of the vehicle system related to the touch control, and the action to be taken by the vehicle system as a result of touching the touch control. In another example embodiment, identify2570may determine which touch control was touched and the further information discussed above.

Activate2572uses the information determined by identify2570to control the vehicle system related to the touch control in the manner specified by the touch control. Activate2572may take such actions as activating, deactivating, changing the operation of, and/or adjusting the operation of the vehicle system related to the touch control.

Dynamic2574determines whether the touch control is a dynamic touch control. If the touch control is a dynamic touch control, update2576is executed to update the image of the icon of the touch control. If the touch control is not a dynamic touch control, control moves to detected2510.

The foregoing description discusses various embodiments, which may be changed or modified without departing from the scope of the present disclosure as defined in the claims. Examples listed in parentheses may be used in the alternative or in any practical combination. As used in the specification and claims, the words ‘comprising’, ‘comprises’, ‘including’, ‘includes’, ‘having’, and ‘has’ introduce an open-ended statement of component structures and/or functions. In the specification and claims, the words ‘a’ and ‘an’ are used as indefinite articles meaning ‘one or more’. While for the sake of clarity of description, several specific embodiments have been described, the scope of the invention is intended to be measured by the claims as set forth below. In the claims, the term “provided” is used to definitively identify an object that is not a claimed element but an object that performs the function of a workpiece. For example, in the claim “an apparatus for aiming a provided barrel, the apparatus comprising: a housing, the barrel positioned in the housing”, the barrel is not a claimed element of the apparatus, but an object that cooperates with the “housing” of the “apparatus” by being positioned in the “housing”.

The location indicators “herein”, “hereunder”, “above”, “below”, or other word that refer to a location, whether specific or general, in the specification shall be construed to refer to any location in the specification whether the location is before or after the location indicator.

Methods described herein are illustrative examples, and as such are not intended to require or imply that any particular process of any embodiment be performed in the order presented. Words such as “thereafter,” “then,” “next,” etc. are not intended to limit the order of the processes, and these words are instead used to guide the reader through the description of the methods.