A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the disclosure herein and to the drawings that form a part of this document: Copyright 2012-2015, CloudCar Inc., All Rights Reserved.
This patent document pertains generally to tools (systems, apparatuses, methodologies, computer program products, etc.) for allowing electronic devices to share information with each other, and more particularly, but not by way of limitation, to a system and method for correcting speech input.
Modern speech recognition applications can utilize a computer to convert acoustic signals received by a microphone into a workable set of data without the benefit of a QWERTY keyboard. Subsequently, the set of data can be used in a wide variety of other computer programs, including document preparation, data entry, command and control, messaging, and other program applications as well. Thus, speech recognition is a technology well-suited for use in devices not having the benefit of keyboard input and monitor feedback.
Still, effective speech recognition can be a difficult problem, even in traditional computing, because of a wide variety of pronunciations, individual accents, and the various speech characteristics of multiple speakers. Ambient noise also frequently complicates the speech recognition process, as the computer may try to recognize and interpret the background noise as speech. Hence, speech recognition systems can often mis-recognize speech input compelling the speaker to perform a correction of the mis-recognized speech.
Typically, in traditional computers, for example a desktop Personal Computer (PC), the correction of mis-recognized speech can be performed with the assistance of both a visual display and a keyboard. However, correction of mis-recognized speech in a device having limited or no display can prove complicated if not unworkable. Consequently, a need exists for a correction method for speech recognition applications operating in devices having limited or no display. Such a system could have particular utility in the context of a speech recognition system used to dictate e-mail, telephonic text, and other messages on devices having only a limited or no display channel.
Many conventional speech recognition systems engage the user in various verbal exchanges to decipher the intended meaning of a spoken phrase, if the speech recognition system is initially unable to correctly recognize the speech. In most cases, conventional systems require that a user utter a separate audible command for correcting the recognized speech. However, these verbal exchanges and audible commands between the user and the speech recognition system can be annoying or even unsafe if, for example, the speech recognition system is being used in a moving vehicle.
The various embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which:
In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It will be evident, however, to one of ordinary skill in the art that the various embodiments may be practiced without these specific details.
As described in various example embodiments, a system and method for correcting speech input are described herein. An example embodiment disclosed herein can be used in the context of an in-vehicle control system. In one example embodiment, an in-vehicle control system with a speech input processing module resident in a vehicle can be configured like the architecture illustrated in
In an example embodiment as described herein, a mobile device with a mobile device application (app) in combination with a network cloud service can be used to implement the speech input correction process as described. Alternatively, the mobile device and the mobile app can operate as a stand-alone device for implementing speech input correction as described. In the example embodiment, a standard sound or voice input receiver (e.g., a microphone) or other components in the mobile device can be used to receive speech input from a user or an occupant in a vehicle. The cloud service and/or the mobile device app can be used in the various ways described herein to process the correction of the speech input. In a second example embodiment, an in-vehicle control system with a vehicle platform app resident in a user's vehicle in combination with the cloud service can be used to implement the speech input correction process as described herein. Alternatively, the in-vehicle control system and the vehicle platform app can operate as a stand-alone device for implementing speech input correction as described. In the second example embodiment, a standard sound or voice input receiver (e.g., a microphone) or other components in the in-vehicle control system can be used to receive speech input from a user or an occupant in the vehicle. The cloud service and/or the vehicle platform app can be used in the various ways described herein to process the correction of the speech input. In other embodiments, the system and method for correcting speech input as described herein can be used in mobile or stationary computing or communication platforms that are not part of vehicle subsystem.
Referring now to
Similarly, ecosystem 101 can include a wide area data/content network 120. The network 120 represents one or more conventional wide area data/content networks, such as the Internet, a cellular telephone network, satellite network, pager network, a wireless broadcast network, gaming network, WiFi network, peer-to-peer network, Voice over IP (VoIP) network, etc. One or more of these networks 120 can be used to connect a user or client system with network resources 122, such as websites, servers, call distribution sites, headend content delivery sites, or the like. The network resources 122 can generate and/or distribute data, which can be received in vehicle 119 via one or more antennas 114. The network resources 122 can also host network cloud services, which can support the functionality used to compute or assist in processing speech input or speech input corrections. Antennas 114 can serve to connect the in-vehicle control system 150 and the speech input processing module 200 with the data/content network 120 via cellular, satellite, radio, or other conventional signal reception mechanisms. Such cellular data or content networks are currently available (e.g., Verizon™, AT&T™, T-Mobile™, etc.). Such satellite-based data or content networks are also currently available (e.g., SiriusXM™, HughesNet™, etc.). The conventional broadcast networks, such as AM/FM radio networks, pager networks, UHF networks, gaming networks, WiFi networks, peer-to-peer networks, Voice over IP (VoIP) networks, and the like are also well-known. Thus, as described in more detail below, the in-vehicle control system 150 and the speech input processing module 200 can receive telephone calls and/or phone-based data transmissions via an in-vehicle phone interface 162, which can be used to connect with the in-vehicle phone receiver 116 and network 120. The in-vehicle control system 150 and the speech input processing module 200 can also receive web-based data or content via an in-vehicle web-enabled device interface 166, which can be used to connect with the in-vehicle web-enabled device receiver 118 and network 120. In this manner, the in-vehicle control system 150 and the speech input processing module 200 can support a variety of network-connectable in-vehicle devices and systems from within a vehicle 119.
As shown in
In various embodiments, the mobile device 130 interface and user interface between the in-vehicle control system 150 and the mobile devices 130 can be implemented in a variety of ways. For example, in one embodiment, the mobile device 130 interface between the in-vehicle control system 150 and the mobile devices 130 can be implemented using a Universal Serial Bus (USB) interface and associated connector. In another embodiment, the interface between the in-vehicle control system 150 and the mobile devices 130 can be implemented using a wireless protocol, such as WiFi or Bluetooth™ (BT). WiFi is a popular wireless technology allowing an electronic device to exchange data wirelessly over a computer network. Bluetooth™ is a well-known wireless technology standard for exchanging data over short distances. Using standard mobile device 130 interfaces, a mobile device 130 can be paired and/or synchronized with the in-vehicle control system 150 when the mobile device 130 is moved within a proximity region of the in-vehicle control system 150. The user mobile device interface 168 can be used to facilitate this pairing. Once the in-vehicle control system 150 is paired with the mobile device 130, the mobile device 130 can share information with the in-vehicle control system 150 and the speech input processing module 200 in data communication therewith.
Referring again to
Referring still to
In the example embodiment shown in
Additionally, other data and/or content (denoted herein as ancillary data) can be obtained from local and/or remote sources by the in-vehicle control system 150 as described above. The ancillary data can be used to augment or modify the operation of the speech input processing module 200 based on a variety of factors including, user context (e.g., the identity, age, profile, and driving history of the user), the context in which the user is operating the vehicle (e.g., the location of the vehicle, the specified destination, direction of travel, speed, the time of day, the status of the vehicle, etc.), and a variety of other data obtainable from the variety of sources, local and remote, as described herein.
In a particular embodiment, the in-vehicle control system 150 and the speech input processing module 200 can be implemented as in-vehicle components of vehicle 119. In various example embodiments, the in-vehicle control system 150 and the speech input processing module 200 in data communication therewith can be implemented as integrated components or as separate components. In an example embodiment, the software components of the in-vehicle control system 150 and/or the speech input processing module 200 can be dynamically upgraded, modified, and/or augmented by use of the data connection with the mobile devices 130 and/or the network resources 122 via network 120. The in-vehicle control system 150 can periodically query a mobile device 130 or a network resource 122 for updates or updates can be pushed to the in-vehicle control system 150.
Referring now to
In an example embodiment as shown in
The input capture logic module 210 of an example embodiment is responsible for obtaining or receiving a spoken base input string. The spoken base input string can be any type of spoken or audible words, phrases, or utterances intended by a user as an informational or instructional verbal communication to one or more of the electronic devices or systems as described above. For example, a user/driver may speak a verbal command or utterance to a vehicle navigation system. In another example, a user may speak a verbal command or utterance to a mobile phone or other mobile device. In yet another example, a user may speak a verbal command or utterance to a vehicle subsystem, such as the vehicle navigation subsystem or cruise control subsystem. It will be apparent to those of ordinary skill in the art that a user, driver, or vehicle occupant may utter statements, commands, or other types of speech input in a variety of contexts, which target a variety of ecosystem devices or subsystems. As described above, the speech input processing module 200 and the input capture logic module 210 therein can receive these speech input utterances from a variety of sources.
The speech input received by the input capture logic module 210 can be structured as a sequence or collection of words, phrases, or discrete utterances (generally denoted objects). As well-known in the art, each utterance (object) can have a corresponding phonetic representation, which associates a particular sound with a corresponding written, textual, symbolic, or visual representation. The collection of objects for each speech input can be denoted herein as a spoken input string. Each spoken input string is comprised of an object set, which represents the utterances that combine to form the spoken input string. It will be apparent to those of ordinary skill in the art in view of the disclosure herein that the spoken input string can be in any arbitrary spoken language or dialect. The input capture logic module 210 of the example embodiment can obtain or receive a spoken input string as an initial speech input for a speech transaction that may include a plurality of spoken input strings for the same speech transaction. An example of a speech transaction might be a user speaking a series of voice commands to a vehicle navigation subsystem or a mobile device app. This aspect of the example embodiment is described in more detail below. As denoted herein, the first speech input from a user for a particular speech transaction can be referred to as the spoken base input string. Subsequent speech input from the user for the same speech transaction can be denoted as the spoken secondary input string or the spoken replacement string. As described in detail below, the input correction logic module 212 of the example embodiment can receive the speech input from the input capture logic module 210 and modify the spoken base input string in a manner that corresponds to the speech input received from the user as the spoken secondary input string or the spoken replacement string.
Referring now to
A conventional automatic speech recognition subsystem can be used to convert the audible utterances into a written, textual, symbolic, or visual representation, such as the text string shown above and in
The sample base input string shown in
Each object of the base object set can have a corresponding phonetic representation. In this example embodiment, the well-known “Refined Soundex” algorithm is used to calculate the phonetic representations of each object. The Refined Soundex algorithm originates from the conventional Apache Commons Codec Language package. The Refined Soundex algorithm is based off of the original Soundex algorithm developed by Margaret Odell and Robert Russell (U.S. Pat. Nos. 1,261,167 and 1,435,663). However, it will be apparent to those of ordinary skill in the art in view of the disclosure herein that another algorithm or process can be used to generate the phonetic representation of the objects in the base input string.
In the example embodiment, the phonetic representations of each of the objects in the base input string are alphanumeric codings that represent the particular sounds or audible signature of the corresponding object.
Referring again to
Many conventional speech recognition systems engage the user in various verbal exchanges to decipher the intended meaning of a spoken phrase, if the speech recognition system is initially unable to correctly recognize the speech. In most cases, conventional systems require that a user utter a separate audible command for correcting the recognized speech. However, these verbal exchanges and audible commands between the user and the speech recognition system can be annoying or even unsafe if, for example, the speech recognition system is being used in a moving vehicle.
The various embodiments described herein enable the user/speaker to initiate a speech correction operation in any of the traditional ways. For example, if the user/speaker uttered a spoken base string that was not recognized correctly by the automatic voice recognition system, the user/speaker can explicitly initiate a speech correction operation by performing any of the following actions: clicking an icon, activating a softkey, pressing a physical button, providing a keyboard input, manipulating a user interface, or uttering a separate audible command for correcting the recognized speech captured as the spoken base input string. In addition, the example embodiments described herein provide an implicit technique for initiating a speech correction operation. In the example embodiment, the implicit speech correction operation is initiated when the user/speaker begins to spell out a word or phrase or the speech recognition subsystem recognizes the spoken utterance of one or more letters. When the user/speaker uses any of these explicit or implicit techniques for initiating a speech correction operation, the input correction logic module 212 can detect the initiation of the speech correction operation. Referring again to
As described above, the user can alternatively spell out the letters of a replacement string using a keyboard, keypad, or other data input device. In this example, the user intends the replacement string of
Referring now to
Referring again to
Referring now to
Referring again to
Referring again to
In an alternative embodiment, the historical data can be used to provide the spoken base input string from a previously issued spoken command or utterance if a portion of the previous utterance matches a newly spoken replacement string. In this embodiment, the user/driver can merely utter a replacement string, such as the sample replacement string (e.g., “xanh”) as described above. In this example embodiment, the user/speaker can initiate the implicit speech correction operation by verbally spelling out letters of the replacement string. In the example described herein, the user/speaker can spell out the following letters in spoken utterances:
As described above, the user can alternatively spell out the letters of a replacement string using a keyboard, keypad, or other data input device. In this example, the user intends the replacement string of the example shown above to be substituted into a previously spoken base input string that has been captured in the historical data set of log database 174. In this case, the user/speaker is not required to repeat the previously spoken base input string. The user is also not required to specify which portion of the previously spoken base input string is to be replaced. Instead, the input correction logic module 212 is configured to automatically find a previously spoken base input string from a historical data set, wherein the previously spoken base input string includes a portion that matches the replacement string. Additionally, the input correction logic module 212 is configured to automatically identify the best match for the replacement string in the previously spoken base input string. Once the matching portion of the previously spoken base input string is identified, the input correction logic module 212 is configured to automatically substitute the replacement string into the matching portion of the previously spoken base input string and process the modified spoken base input string as a new command or utterance. In the example embodiment, the input correction logic module 212 is configured to initially attempt to match the newly spoken replacement string to a most recently spoken base input string. If a match between the newly spoken replacement string and a portion of the most recently spoken base input string cannot be found, the input correction logic module 212 is configured to attempt to match the newly spoken replacement string to the previously spoken base input strings retained in the historical data set. In this manner, the user/speaker can utter a simple replacement string, which can be automatically applied to a current or historical base input string. A flowchart of this example embodiment is presented below in connection with
Referring now to
Thus, as described herein in various example embodiments, the speech input processing module 200 can perform speech input correction in a variety of ways. As a result, the various embodiments allow the user/machine voice transaction to become more efficient, thereby increasing convenience, and reducing potential delays and frustration for the user by introducing predictive speech processing.
Referring now to
Referring now to
As used herein and unless specified otherwise, the term “mobile device” includes any computing or communications device that can communicate with the in-vehicle control system 150 and/or the speech input processing module 200 described herein to obtain read or write access to data signals, messages, or content communicated via any mode of data communications. In many cases, the mobile device 130 is a handheld, portable device, such as a smart phone, mobile phone, cellular telephone, tablet computer, laptop computer, display pager, radio frequency (RF) device, infrared (IR) device, global positioning device (GPS), Personal Digital Assistants (PDA), handheld computers, wearable computer, portable game console, other mobile communication and/or computing device, or an integrated device combining one or more of the preceding devices, and the like. Additionally, the mobile device 130 can be a computing device, personal computer (PC), multiprocessor system, microprocessor-based or programmable consumer electronic device, network PC, diagnostics equipment, a system operated by a vehicle 119 manufacturer or service technician, and the like, and is not limited to portable devices. The mobile device 130 can receive and process data in any of a variety of data formats. The data format may include or be configured to operate with any programming format, protocol, or language including, but not limited to, JavaScript, C++, iOS, Android, etc.
As used herein and unless specified otherwise, the term “network resource” includes any device, system, or service that can communicate with the in-vehicle control system 150 and/or the speech input processing module 200 described herein to obtain read or write access to data signals, messages, or content communicated via any mode of inter-process or networked data communications. In many cases, the network resource 122 is a data network accessible computing platform, including client or server computers, websites, mobile devices, peer-to-peer (P2P) network nodes, and the like. Additionally, the network resource 122 can be a web appliance, a network router, switch, bridge, gateway, diagnostics equipment, a system operated by a vehicle 119 manufacturer or service technician, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” can also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. The network resources 122 may include any of a variety of providers or processors of network transportable digital content. Typically, the file format that is employed is Extensible Markup Language (XML), however, the various embodiments are not so limited, and other file formats may be used. For example, data formats other than Hypertext Markup Language (HTML)/XML or formats other than open/standard data formats can be supported by various embodiments. Any electronic file format, such as Portable Document Format (PDF), audio (e.g., Motion Picture Experts Group Audio Layer 3—MP3, and the like), video (e.g., MP4, and the like), and any proprietary interchange format defined by specific content sites can be supported by the various embodiments described herein.
The wide area data network 120 (also denoted the network cloud) used with the network resources 122 can be configured to couple one computing or communication device with another computing or communication device. The network may be enabled to employ any form of computer readable data or media for communicating information from one electronic device to another. The network 120 can include the Internet in addition to other wide area networks (WANs), cellular telephone networks, metro-area networks, local area networks (LANs), other packet-switched networks, circuit-switched networks, direct data connections, such as through a universal serial bus (USB) or Ethernet port, other forms of computer-readable media, or any combination thereof. The network 120 can include the Internet in addition to other wide area networks (WANs), cellular telephone networks, satellite networks, over-the-air broadcast networks, AM/FM radio networks, pager networks, UHF networks, other broadcast networks, gaming networks, WiFi networks, peer-to-peer networks, Voice Over IP (VoIP) networks, metro-area networks, local area networks (LANs), other packet-switched networks, circuit-switched networks, direct data connections, such as through a universal serial bus (USB) or Ethernet port, other forms of computer-readable media, or any combination thereof. On an interconnected set of networks, including those based on differing architectures and protocols, a router or gateway can act as a link between networks, enabling messages to be sent between computing devices on different networks. Also, communication links within networks can typically include twisted wire pair cabling, USB, Firewire, Ethernet, or coaxial cable, while communication links between networks may utilize analog or digital telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital User Lines (DSLs), wireless links including satellite links, cellular telephone links, or other communication links known to those of ordinary skill in the art. Furthermore, remote computers and other related electronic devices can be remotely connected to the network via a modem and temporary telephone link.
The network 120 may further include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection. Such sub-networks may include mesh networks, Wireless LAN (WLAN) networks, cellular networks, and the like. The network may also include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links or wireless transceivers. These connectors may be configured to move freely and randomly and organize themselves arbitrarily, such that the topology of the network may change rapidly. The network 120 may further employ one or more of a plurality of standard wireless and/or cellular protocols or access technologies including those set forth herein in connection with network interface 712 and network 714 described in the figures herewith.
In a particular embodiment, a mobile device 130 and/or a network resource 122 may act as a client device enabling a user to access and use the in-vehicle control system 150 and/or the speech input processing module 200 to interact with one or more components of a vehicle subsystem. These client devices 130 or 122 may include virtually any computing device that is configured to send and receive information over a network, such as network 120 as described herein. Such client devices may include mobile devices, such as cellular telephones, smart phones, tablet computers, display pagers, radio frequency (RF) devices, infrared (IR) devices, global positioning devices (GPS), Personal Digital Assistants (PDAs), handheld computers, wearable computers, game consoles, integrated devices combining one or more of the preceding devices, and the like. The client devices may also include other computing devices, such as personal computers (PCs), multiprocessor systems, microprocessor-based or programmable consumer electronics, network PC's, and the like. As such, client devices may range widely in terms of capabilities and features. For example, a client device configured as a cell phone may have a numeric keypad and a few lines of monochrome LCD display on which only text may be displayed. In another example, a web-enabled client device may have a touch sensitive screen, a stylus, and a color LCD display screen in which both text and graphics may be displayed. Moreover, the web-enabled client device may include a browser application enabled to receive and to send wireless application protocol messages (WAP), and/or wired application messages, and the like. In one embodiment, the browser application is enabled to employ HyperText Markup Language (HTML), Dynamic HTML, Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript, EXtensible HTML (xHTML), Compact HTML (CHTML), and the like, to display and send a message with relevant information.
The client devices may also include at least one client application that is configured to receive content or messages from another computing device via a network transmission. The client application may include a capability to provide and receive textual content, graphical content, video content, audio content, alerts, messages, notifications, and the like. Moreover, the client devices may be further configured to communicate and/or receive a message, such as through a Short Message Service (SMS), direct messaging (e.g., Twitter), email, Multimedia Message Service (MMS), instant messaging (IM), internet relay chat (IRC), mIRC, Jabber, Enhanced Messaging Service (EMS), text messaging, Smart Messaging, Over the Air (OTA) messaging, or the like, between another computing device, and the like. The client devices may also include a wireless application device on which a client application is configured to enable a user of the device to send and receive information to/from network resources wirelessly via the network.
The in-vehicle control system 150 and/or the speech input processing module 200 can be implemented using systems that enhance the security of the execution environment, thereby improving security and reducing the possibility that the in-vehicle control system 150 and/or the speech input processing module 200 and the related services could be compromised by viruses or malware. For example, the in-vehicle control system 150 and/or the speech input processing module 200 can be implemented using a Trusted Execution Environment, which can ensure that sensitive data is stored, processed, and communicated in a secure way.
The example mobile computing and/or communication system 700 can include a data processor 702 (e.g., a System-on-a-Chip (SoC), general processing core, graphics core, and optionally other processing logic) and a memory 704, which can communicate with each other via a bus or other data transfer system 706. The mobile computing and/or communication system 700 may further include various input/output (I/O) devices and/or interfaces 710, such as a touchscreen display, an audio jack, a voice interface, and optionally a network interface 712. In an example embodiment, the network interface 712 can include one or more radio transceivers configured for compatibility with any one or more standard wireless and/or cellular protocols or access technologies (e.g., 2nd (2G), 2.5, 3rd (3G), 4th (4G) generation, and future generation radio access for cellular systems, Global System for Mobile communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (WCDMA), LTE, CDMA2000, WLAN, Wireless Router (WR) mesh, and the like). Network interface 712 may also be configured for use with various other wired and/or wireless communication protocols, including TCP/IP, UDP, SIP, SMS, RTP, WAP, CDMA, TDMA, UMTS, UWB, WiFi, WiMax, Bluetooth©, IEEE 802.11x, and the like. In essence, network interface 712 may include or support virtually any wired and/or wireless communication and data processing mechanisms by which information/data may travel between a mobile computing and/or communication system 700 and another computing or communication system via network 714.
The memory 704 can represent a machine-readable medium on which is stored one or more sets of instructions, software, firmware, or other processing logic (e.g., logic 708) embodying any one or more of the methodologies or functions described and/or claimed herein. The logic 708, or a portion thereof, may also reside, completely or at least partially within the processor 702 during execution thereof by the mobile computing and/or communication system 700. As such, the memory 704 and the processor 702 may also constitute machine-readable media. The logic 708, or a portion thereof, may also be configured as processing logic or logic, at least a portion of which is partially implemented in hardware. The logic 708, or a portion thereof, may further be transmitted or received over a network 714 via the network interface 712. While the machine-readable medium of an example embodiment can be a single medium, the term “machine-readable medium” should be taken to include a single non-transitory medium or multiple non-transitory media (e.g., a centralized or distributed database, and/or associated caches and computing systems) that store the one or more sets of instructions. The term “machine-readable medium” can also be taken to include any non-transitory medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the various embodiments, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term “machine-readable medium” can accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.
The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
This is a continuation-in-part patent application of co-pending U.S. patent application Ser. No. 13/943,730; filed Jul. 16, 2013 by the same applicant. This is also a non-provisional patent application drawing prior from co-pending U.S. provisional patent applications, Ser. Nos. 62/115,400 and 62/115,406; both filed Feb. 12, 2015 by the same applicant. This present patent application draws priority from the referenced patent applications. The entire disclosure of the referenced patent applications is considered part of the disclosure of the present application and is hereby incorporated by reference herein in its entirety.
Number | Date | Country | |
---|---|---|---|
62115400 | Feb 2015 | US | |
62115406 | Feb 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13943730 | Jul 2013 | US |
Child | 14855295 | US |