Our Trade Names
Updated 20170821 @ 6:21 PM/CT
The Following TradeNames are Protected By:
AUTHORIZATION PURSUANT TO 37 C.F.R. §1.171 (d)
Portions of the disclosure of this patent document contains material which is subject to copyright and trademark 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 Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.
|
iDomains |
Absolute eComm-device Directory Trail |
Administers Organizational Control |
Administers Organizational Control |
AiChipSet |
Artifact Repositories |
Assessment-Platform |
Authoritative Encrypted Digital Traffic Directives |
AutoVector Identified Chip Set (AIChipSet) |
Certified Compliant Smart eComm-devices |
certified smart devices |
Channeled Communication Device |
Channeled Telematic Infrastructure |
Channeled Telematics |
Channeled Telematics by subnavsys integration |
Channeled Vehicular Telematics |
Cloud Sync’d Enterprise Architecture |
Comparison Index |
Connected Channelled Intelligence |
Consumption Momentum Rate |
Consumption Variable Analysis |
Creation Inception Point |
Crypsis Tokenization |
CybrCloud |
CybrIntelligence |
Dedicated Lane Isolation |
Density Factor |
Density Point Clustering Schema – (DPCS) |
Determined Route Alternative |
Device System Controller (syscon) |
Drive Secure & Safe |
Drone Intrusion Detection and Disruption |
Encrypted Data Communication Link (edcomm-link) |
Encrypted Data Push |
Fuel Supply iPoints |
Geographical Informational Location (GeoiLoc) |
GeoiLoc vector area |
GeoLoc-Nodes |
GeoLocNode (GLN) |
Geotraffic Locational Momentum |
I2I |
iBreaking System (IBS) data-link |
iCP |
Identified Locked and Secure (iLocSec) |
iDentified Transport |
iDomain |
iGATE |
iGrid |
Igrid-Matrix |
iKey-set directory |
iKeyset shell repository |
iKnowledge (iK) |
iLink-sync'd |
iLink-sync'd tLoad Stand |
iLinked clustered mass |
iLinkSync’d |
iLinkSync’d (Identified Link Synchronized Device) |
iLogic-gates |
iMapTrac |
iMarker(s) |
iMechanizm |
iMechanizm (ITD) |
iMechanizms computer processor(s) (iCP) |
Implied Intelligent Telematic Integrity |
iNetworked |
iNetworked iDomains |
Infrastructure2Vehicle |
Intelligent Telematic Model - ITM |
intuitive traffic systems |
Intuitive Transport Management |
IPNode |
iRoute-path |
iRoutine |
ITD (Intelligent Transmitted Data) |
iTrace iRoute-iPath |
iTrace-route |
iTransports |
iVDomain |
iVectorShield (iVS) |
iX2 |
iXfactors relationship to X2Factors, vehicles (X3) factors, telemetry capabilities and topo-matic conditions. |
Key-Code |
Load-Network |
Load-Networked |
Logical Virtual Network Topology (LVNT) |
Longlatilt |
Map-track |
Map-tracking |
Map-tracking |
Markers |
Match-points |
Matched Key-Set |
Merchant Purveyor |
Mobile Vector Domain Pilot |
mVector-Domain (MVD) |
Navigational Matrix |
Network Packet Artifacts (NPA) |
ODNA directory |
On Demand Network Advertising (Advertisements) |
Open Intelligent System (OIS) |
Origination Creation Inception Point |
Paired-key |
pAvics |
Phase Shift |
Phase-change Shift |
Phase-Change spatial position |
Private Encrypted Repositories (PERP) |
Propositional Configuration |
Proximitry Sensors co |
Quantum Positioning Overlay Model |
Read Only Accessibility Privilege |
Registered Sync’d Authenticated Paired |
Reliable by Design |
Response Key-set (RKS) |
iPNode |
Fuel Supply iPoints |
Rudimentary Infrastructure |
SAUBI |
secure infrastructure |
Secure Point Communication (SPC) |
select on demand advertisement service (SODAS) |
Sentinel-Code |
Smarter Processing Platform |
Spatial Conformity |
Spatial Density Momentum |
Spatial Positional Change |
Statistical Telematic Analytical Data |
Structured Navigational Matrix |
Sub-iRoutine |
SubHub-Class Device |
Telemetry amplification |
Telemetry mobility |
Telemetry Network Topology |
Telemetry spectrum |
Telespect, short for Telemetry Spectrum. |
Time-Point |
tLoad Stand |
tMarker and t2Marker |
tMarker Audit Trail |
tMarker index |
tMarker trail, Time trail – t2Marker |
tMarkerTrail |
tMarkerTrail |
Touch-View-Print |
Trace Route-path |
Traffic Infrastructure Hubs |
Trail Date |
tRoute Marker’, ’t’ stands for time-stamp - TRM |
Ultrasonic telemetry-device |
Uniform Vehicular Architecture (UVA) |
Var Chk Index |
VCPI (Virtual Cryptic Private Infrastructure) |
Vector Locator Path – VLP |
VectorArc-Objects |
VectorNode |
Vehicle-domains |
Vehicle-iDomains |
Virtual Assessment-Platform (VAP) |
Virtual Class Nodes (vCNode) |
Virtual Conceptual Interface (VCI) |
Virtual Interactive Reality (VIR) Inter-FACE |
Virtual Private Infrastructure (VPI) |
Virtual Telematic Connectivity |
vNode |
VTA |
x2Factors |
Updated 20161021 @ 10:34 AM/CT
One may wonder why we are listing our trade names; over the course to the past few years one or more of our trade names were used inappropriately on one or more social media sites, e.g. CybrIntelligence™ used without our permission; this is standard business practice on social media sites; wherein CyberGangBangers™ have zero integrity, even after asking some to remove our name; wherein trying to contact someone is always difficult and or hidden. Even one or more search engines BING, GOOGLE really do not care if your trade name is used by anyone else, even though they have 10’s of thousands of employees, most assuredly at least one would or have access to check and or challenge the use of other companies trade names being used by others or better yet a simple spider to verify same when listing site with search engines, they really don't care for a multitude of reasons. What makes things even more absurd, we have been fortunate that a few of our domains and or trade names are able to be found on search results by others; wherein most of the name below if searched can't be found, even though a lot these phases and or names are in two of the four patents currently public. Personally this is merely pure JEG (Jealousy, Envy and or Greed) in their reasoning as to why they restrict our trade names. How funny, [I]f you do not care to play the key word list game it should not matter, whether any specific name and or a string of names, especially that describes something [i]f searched by anyone a result should display, especially if it the exact word with a string of words - not the case with most of our trade names below; some of the results one gets is 'does not exist', even though the name and or phrase has residence.
The item that would disgust most is that over the past 4-5 months we have collected multiple pdf’s of the main page, Xgenasys.com; the searched results show that the searched name: Xgenasys™ just disappears from from time to time on all search engines periodically. Until site gets resubmitted again with Bing at URL: ( http://www.bing.com/toolbox/submit-site-url ), about every 7-10 or so the site disappears again, not sure why. The day these words were herein stated the URL was not available on: 20160808-T3:37:34 , the site was submitted again and checking at 20160808-T6:15:23 , 3 hours later the site was back up. On the other hand, google searched results collected over the past five years or so, show an extreme case; wherein the site is placed with sites such as how much the site is worth, is it safe to navigate and so on; do other sites get the similar treatment - can't find any. Further searches for other site name show other results not even closely related to with all the non related ancillary sites.
Just like AT&T, are they really a secure gate keeper provider, even though they sit on or have control over most of the internet (and should not be the case) everyone reading this page and all your friends and family members and all there relatives, co-worker and families an so on; use AT&T and other similar providers, need to thank for not protecting their PC, MAC, etc. since they (AT&T) are one of the main gate keepers herein the US. Meaning, each of us has to purchase hardware and or software that protects our assets, e.g. personal PC and or our business networks. Meantime, AT&T, Verizon and so on has routers and switches, so do hosting companies that could very simply stop / block / bounce and so forth all know IP BLOCKS of known hackers from e.g. http://www.nirsoft.net/countryip/ , http://spamassassin.apache.org, http://www.backscatterer.org, http://barracudacentral.org/rbl, etc. Over the past decade, we have employed devices from AT&T, Comcast, etc. and their routers the provide to customers, the tech's installing and or customer service (CSR) never assist with closing all doors on the device; wherein customer once device is turned on is has all sorts of ports open for hackers to breach - again they, the providers just pass the buck onto the consumer. [T]his one event identifying email spammers and other malicious attack routes and so on; they don’t care to.This burden is pushed off onto the consumer; wherein as history and statistical data provide over half+ {more like 75%) of all PC’s, etc. are or have been compromised with viruses, worms, trojans, etc.; but yet the providers simply ignore their ethical obligation to provide clean data access; wherein they can see and know of these attacks routes/IP’s, etc. and do nothing; including all the hosting companies that allow nearly 75%+ of all the spam emailers access to choke the net down and your email inbox also. Currently there is no way to opt-out, if continued to disrespect others rights; then their names, etc. are put on a list for other companies not to allow service…and most likely some form thereof will arrive soon. By the way, there is no need to accept cookies at all, they track your IP address and the sites you go to without the cookies - fact! Unless you go through a proxy server to do your searches -
I have asked at least two AT&T reps’ this question over the past three years, each have a ‘da’ response such as: good question, not sure, there is a privacy issue (BS for sure) - I jumped on this response, a negative reaction followed with each. Well folks, if we are paying for internet connectivity should it not be screened/protected by the provider before data is allowed to be transmitted back to or sent from you; most would be inclined to agree. If they have 1 million users, that’s a lot of money generated if only charged say ten dollars, equals 10 mil per month to provide this small risk deterrent; you think that this amount would pay for the software/hardware - believe it, it would! Most of the infrastructure is in place now, but they want initialize protection.
BACK TO Xgenasys™
Search engines reasoning in handling a websites content, document, etc. in equal standing, the mannerism is vague at best and should not be the case! Any created material idea of any type, documents and such as the patents that have been granted thus far and those in the que for review and other notable informational items that are original - de-ranking sites that simply regurgitates original source is necessary in providing transparent viable information.
Let’s flip the script, if a large company came up with a unique name/slogan a string of words that described a process and so forth, etc. and placed a ™ behind the name, most assuredly everyone would back off from using that name and the search engines/hosting companies most likely would not allow it. However this is not the case, if its a small company, you have these roach-cocks, that invariably will create an account on a anti-social media sites; wherein the company could really care less an never verifies, to cause as much harm as possible.
This system far reaches beyond the scope of normalcy, the vehicular ‘navigational platform’ system™ discussed in all patents build an infrastructure not contemplated before now, formulated the necessary protection afforded each vehicle consumer and or business owner transporting commerce. Further, it is felt inside, this platform system should be a culmination of many patents incorporating the benefits thereof, not just a few. Mankind is approaching a window in space time; wherein current social obstacles in play in relationship with prior dated times in history, the results are very similar - simply over.
Xgenasys™, the system was created initially from an event that took place back in June ’09, when I was traveling to visit my mom in a assisted living facility; wherein when I took a right on green, however during the turn the light started to change yellow. This is where it gets good; upon completing the turn, I traveled about a hundred feet, put left blinker on moved into left lane nearly half my truck was in the left lane, a car moving rapidly through the intersection ( as many of us have done ) catching the light sequence just right and never slowing down, drove up onto left curb tearing up her rims and tires on left side, just to get around me, even though I was moving into left lane. For the record she was on two phones at the same time.
Traffic, at the intersection behind became seriously congested at three points, I called 911 requesting an officer and within a few more minutes people began honking and slurring malicious words: ‘move your freecken truck, etc.’. The traffic congestion became so bad, the emergency vehicles had to drive in the wrong way. e.g. approaching from our front, even though we were on a two lane divided street. The 911 operator instructed me to move my truck, due to all the calls coming in.
This is where it gets pathetic, once moved into a shopping center parking lot just less than a hundred feet in front of us; the officers stated that he could not write a report: since you moved your vehicle - this made me so nauseated and angry; wherein I began to write the basis for Nxgen Traffic System™ - two pages and will post on Xgenasys’s new site in the near future. This same sort of incident happened to my daughter in Austin on Guadalupe; wherein tow girls in a car turned into her left side; and she did not move her car until 911 operator told her too, since traffic was being blocked on both lanes. Again after the above mentioned accident, a young driver with Dallas Doors migrated new one ton flat bed truck with a 3 inch plate around perimeter of bed - that stuck out beyond rear tires ~ 4-5 inches. The imapct hit left fender and tore of front headlight assembly damaging the left front fender on truck. Each of these occurrences the drivers were on their cellphones and a written report was sent to State Farm for each event, requesting that they pull phone records, this was never done an should be mandatory - the requests were ignored each time.
Realizing that this type of situation occurs routinely, including being rear ended, hit an run situation, lack of vehicles not carrying current insurance and the problems with connecting cars will be a whacker-hackers dream land; the traffic system most be a closed environment, preferably encrypted; wherein communication devices can only communicate with/to other devices equipped with a Nuclex Operating System™, each certified ecomdevice™ have gone through several security protocols, e.g. authentication, registration and each are ilink-sync’d™ with not only each navigational transmitting device including each Transport iMechanizm™, but also the system itself. Otherwise chaos results, since we all know there will be a few that try to screw things up for the many. The system reflects air navigation, it too is a closed environment.
The reason why I made the statement regarding the system being Open Source Registered Platform™ (OSRP™), thinking for the benefit of each driver that has experienced similar occurrences stated previously; the negative undertones from larger corporations is not only amazing, again it is standard business practice to deliberately cause harm to others for whatever reason. Perplexing as it is, one would think since MicroSoft announced access to their patents, Toyota back in February '15 announced 6500 patents, anyone could use them and moving into Hydrogen vehicle propulsion is the future of transportation, then came Tesla making a similar statement: the world has access to all our patents, including battery systems; why are one or more of these entities causing so much grief with Transparent Information - please explain, the decision of the law is not adequate.
Thinking waay outside the box; wherein our ancestors built a device that can put an end to this planet and the humans that occupy same; contemplating that other companies would step up or reach out to drive this system beyond imagination, may not be the case. Therefore, reaching out side USA to other companies/countries may be an alternative in the near future.
Within less than 3 hours the page is listed, hmmmm can you feel it or not - the hand? On or about Aug. 19th 2016 in the afternoon hours, all search engines removed the searched result name: Xgenasys™, this is purely an aggressive tactic one would not see in a democracy.
∆
AUTHORIZATION PURSUANT TO 37 C.F.R. §1.171 (d)
One or more of the below trade names are subject to copyright and trademark 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 Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.
~
∑Ω Sum of Alpha™ |
FIRST USE: 20160308. FIRST USE IN COMMERCE: 20160308 |
Knowledge, the outer edge of reality™ |
FIRST USE: 20160103. FIRST USE IN COMMERCE: 20160103 |
Advance Analytical Routing Alternatives™ |
FIRST USE: 20150120. FIRST IN COMMERCE: 20150120 |
Advance Congestion Flow Routes™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Advanced Network Routing Alternatives™ |
|
Advanced Analytical Routing Alternatives™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
AdvertisingHub(s)™ |
FIRST USE: 20160704. FIRST IN COMMERCE: 20160704 |
AdvertisingNode(s)™ |
FIRST USE: 20160704. FIRST IN COMMERCE: 20160704 |
AlphaHubs™ |
FIRST USE: 20090713. FIRST IN COMMERCE: 20090713 11:15:50Z |
AlphaVectorHub™ |
FIRST USE: 20140701. FIRST USE IN COMMERCE: 20140701 |
AlphaVectorHubs™ |
FIRST USE: 20140701. FIRST USE IN COMMERCE: 20140701 |
Analytical Automated Option Response™ |
FIRST USE: 20150120. FIRST IN COMMERCE: 20150120 |
Analytical Variable Data Checks™ |
FIRST USE: 20150120. FIRST IN COMMERCE: 20150120 |
Architectural Application Reliability™ |
FIRST USE: 20140125. FIRST IN COMMERCE: 20140125 T03:30:13Z |
Auto Vector Identified Chipset™ |
FIRST USE: 20160615. FIRST IN COMMERCE: 20160615 |
Autonomous User Based Insurance™ AUBI™ |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160101 |
Autovecth™ (AutoVector Traffic Hub™) |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Authoritative Encrypted Digital Traffic Directives™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Avics™ Avics(RFIDGPS)™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
BeaconHub™ |
FIRST USE: 201110602. FIRST IN COMMERCE: 20111060 T17:48:17Z |
BeaconHub Nodes™ |
FIRST USE: 20150822. FIRST USE IN COMMERCE: 20150822 |
BeaconHubs™ |
FIRST USE: 20140701. FIRST USE IN COMMERCE: 20140701 |
BeaconNodes™ |
FIRST USE: 20150822. FIRST USE IN COMMERCE: 20150822 |
Business Telematic Intelligence™ BTI™ |
FIRST USE: 20150809. FIRST IN COMMERCE: 20150809 |
Channeled Telematic Weather™ |
FIRST USE: 20150323. FIRST IN COMMERCE: 20160219 |
Channeled Telematics™ |
FIRST USE: 20150128. FIRST IN COMMERCE: 20150128 T18:49:T04Z |
Cloud Matrix Servers™ |
FIRST USE: 20150128. FIRST IN COMMERCE:20150128 218:49:04Z. |
Cloud Sync Based Enterprise™ |
FIRST USE: 20160205. FIRST IN COMMERCE:20160205 218:49:04Z. |
Computational Traffic Flow Dynamics™ |
FIRST USE: 20121007. FIRST USE IN COMMERCE: 20121007 |
Constructed Network Protocol™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Creation Inception Point™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Crypsis Cipher Key'™ |
FIRST USE: 20120620. FIRST USE IN COMMERCE: 20120620 |
Crypsis Data™ |
FIRST USE: 20120717. FIRST IN COMMERCE: 20120717 T19:27:52Z |
Cryptic Communications™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Crypsis Tokenization™ |
FIRST USE: 20130913. FIRST IN COMMERCE: 20130913 T18:13:40Z |
Crypsis Cipher Key™ |
FIRST USE: 20120620. FIRST USE IN COMMERCE: 20120620 |
CybrCloud™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
CybrIntelligence™ The Balance of Human Knowledge merged with Machine Language™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Data Integrity Composition™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Data Integrity Composition Inspections™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Dcomm-device™ {Data Communication Device™} |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160219 |
Domain Networked Infrastructure™ |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160219 |
Data Symmetry Gateways Links™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Direct Point Communication™ |
FIRST USE: 20160718. FIRST USE IN COMMERCE: 20160718 |
Dynamic Analytical Lane Allocations™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Dynamic Lane Allocations™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Dynamic Analytical Rate Flow™ DARF™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Dynamic Algorithmic Architecture™ |
IRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
|
Dynamic Directional Flow Constraints™ DDFC™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Encrypted Communication Device™ {ecomm-device(s)}™ |
|
Encrypted Data Push™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Authoritative Encrypted Digital Traffic Directives™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Encrypted Traffic Data Repositories™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Encrypted Data Communication Links™ edcommlinks™ or EDCLink™ |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160219 |
Energy Summation Data™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Energy Propulsion Data™ |
FIRST USE: 20160925. FIRST IN COMMERCE: 20160925 |
Fossil Fuel Supply Consumption Rate™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
IChipSet™ / Integrated Identified Circuits™ |
FIRST USE: 20150120. FIRST IN COMMERCE: 20150120. T20:18:22Z |
iChipsetX / One or more 'Integrated Stacked Identified Circuits'™ |
FIRST USE: 2015. FIRST IN COMMERCE: 2015 |
Ideate Intelligence™ |
FIRST USE: 20160318. FIRST USE IN COMMERCE: 20160318 |
iNavCom™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
iNavx2™ |
FIRST USE: 20160125. FIRST IN COMMERCE: 20160125 214:09:12Z |
Integrity builds Heritage™ |
FIRST USE: 20150917. FIRST USE IN COMMERCE: 20150917 |
International Transit Telematic System™ ITTS™ |
FIRST USE: 20160213. FIRST USE IN COMMERCE: 20160213 |
Transport iMechanizm™ |
FIRST USE: 20160804. FIRST IN COMMERCE: 20160804. |
Intuitive ITS™ |
FIRST USE: 20160213. FIRST USE IN COMMERCE: 20160213 |
Intuitive Transit Telematics™ |
FIRST USE: 20160213. FIRST USE IN COMMERCE: 20160213 |
iVocx™ |
FIRST USE: 20130207. FIRST IN COMMERCE: 20130207 T22:23:31Z |
iVoiceCommand® |
FIRST USE: 20120112. FIRST IN COMMERCE: 20120112 T18:37:36Z |
iVotronix™ |
FIRST USE: 20120112. FIRST IN COMMERCE: 20120112 T18:37:00Z |
Link-Syncd™ |
|
Link-Sync-d™ |
|
Link-sync'd™ |
|
Logical Conceptual Design™ |
FIRST USE: 20130918. FIRST IN COMMERCE: 2013091 T18:13:41Z |
Logically Morphed Datasets™ |
|
Lucidly Optimized™ |
|
Manage Autonomous User Based Insurance™ MAUBI™ |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160101 |
Network Traffic Artifacts™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Network Traffic Congestion Artifacts™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
NuClex Operating System™ (NOS™) |
FIRST USE: 20140118. FIRST IN COMMERCE: 20140118 |
NxGen Traffic System™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Object Functionality Point(s)™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Obvipro™ {OnBoard Vehicle Processor™} |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Open Source Registered Platform™ (OSRP)™ |
FIRST USE: 20141218. FIRST IN COMMERCE: 20141218. |
Proximitry Integration™ |
FIRST USE: 2014091202. FIRST IN COMMERCE: 20141202 |
Portable Avics™ pAvics™ |
FIRST USE: 2014091202. FIRST IN COMMERCE: 20141202 |
Qualitative Conjectured Route Suggestions™ |
FIRST USE: 2014091202. FIRST IN COMMERCE: 20141202 |
Quantum Mathematical Boundaries™ |
|
Quantum Telematic(s) Network™ |
FIRST USE: 2014091202. FIRST IN COMMERCE: 20141202 |
Quantum Vector Nodes™ |
FIRST USE: 2014091202. FIRST IN COMMERCE: 20141202 |
Rapid Traffic Congestion Flow Analysis™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Reactive Response Interval Feeds™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Recommended Traffic Congestion Options™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Smarter Traffic Ecosystem™ |
FIRST USE: 20160814. FIRST USE IN COMMERCE: 20160814 |
Secure Capacity Storage™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Secure Point Communication™ |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160219 |
SentinelHub™ |
FIRST USE: 20111215. FIRST USE IN COMMERCE: 20111215 T21:55:Z53 |
SentinelHubs™ |
FIRST USE: 20140812. FIRST USE IN COMMERCE: 20140812T21:55:Z53 |
SentinelNodes™ |
FIRST USE: 20140701. FIRST USE IN COMMERCE 20140701 |
SentryBeacon(s)™ |
FIRST USE: 20140812. FIRST USE IN COMMERCE: 20140812 T18:41:Z56 |
SiliconiTValley™ life thrives outside the box™ |
FIRST USE: 20140625. FIRST IN COMMERCE: 2014062 20:50:47Z |
Structured Network Packet Knowledge™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Sub Navigational Systems™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Sub-Class Device™ |
|
Subhub-Class™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Subnavsys™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
Telematic Virtual Architecture™ interface known as tVArc™ (further known as TVA™) |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160219 |
Telemetry Mobility™ |
FIRST USE: 20160807. FIRST USE IN COMMERCE: 20160807 |
TRAFFIC VARIABLE SENSITIVITY SENSORS™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Topography and Climatic Expectations™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
TRAFFIC CONGESTION ARTIFACTS™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Traffic Light Fragmentation™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Traffic Navigational Matrix™ |
FIRST USE: 20160308. FIRST USE IN COMMERCE: 20160308 |
Traffic Variable Sensitivity Sensors™ |
FIRST USE: 20160308. FIRST USE IN COMMERCE: 20160308 |
Transparent Informational Knowledge™ |
FIRST USE: 20120717. FIRST USE IN COMMERCE: 20130915 |
Transport iMechanixm™ |
FIRST USE: 20160808. FIRST USE IN COMMERCE: 20160808 |
FIRST USE: 20121006. FIRST USE IN COMMERCE: 201121006 T21:18:08Z |
|
tVectorHubs™ |
FIRST USE: 20121006. FIRST USE IN COMMERCE: 201121006 T21:18:08Z |
Variable Bandwidth Segregation™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Variable Traffic Flow Analysis™ |
FIRST USE: 20091006. FIRST IN COMMERCE: 20121006 |
Vector-Class Devices™ |
FIRST USE: 20150323. FIRST USE IN COMMERCE: 20160219 |
VectorHub™ |
FIRST USE: 20140701. FIRST USE IN COMMERCE: 20140701. T20:14:29Z |
VectorHubs™ |
FIRST USE: 20140701. FIRST USE IN COMMERCE: 20140701. T20:14:29Z |
Vehicular Traffic Evolution™ |
FIRST USE: 20160802. FIRST USE IN COMMERCE: 20160802. |
Virtual Telematic Connectivity™ |
|
Xgenaasys™ |
FIRST USE: 20091009. FIRST IN COMMERCE: 20121006 |
AUTHORIZATION PURSUANT TO 37 C.F.R. §1.171 (d)
Portions of the disclosure of this patent document contains material which is subject to copyright and trademark 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 Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.
~