Building mobile apps via Compound Wireless Services

Mobile applications (apps), because of their utility, are receiving considerable attention. Manufacturers of mobile terminals and cellular service providers advertise their apps and thereby create incentives to sell their terminals/services. Although the apps being built possess options to alter their specific behavior, they are not designed to link with apps developed by other entities. Unless development coordination exists between the two entities, it is unlikely that an app built by one entity can be compatibly linked to an app built by another entity. A major feature of Compound Wireless (Mobile Communication) Services (CWSs) is to facilitate the linking of apps without requiring development coordination between the entities responsible for the apps to be linked. Currently apps are built with line coding and using the tool kits provided by the terminal manufacturers or mobile operating systems providers. This limits apps building to those trained in this discipline and have established a financial relationship with terminal manufacturers/ mobile operating systems providers. An intuitive graphical approach exists for building CWS apps. Hence, building and linking CWS apps becomes possible without extensive training and includes most owners of the mobile terminals. As a background, CWS derives its name from grammar. A simple sentence consists of a single assertion; e.g., "I am going to the store." The use of connectives, such as "and", "or" 'if ..., then", allow the linking of assertions to form compound sentences; e.g., "I am going to the store and I will buy milk." Analogously, a CWS is formed by linking services with connectives. A CWS's roots consist of "Fundamental Wireless Services" (FWS) that correspond to single assertions; e.g., "determine time of day", "telephone a number", "announce a recorded message". The FWSs are line coded services. Connectives are used to graphically link the FWSs and thereby build a CWS. Just as in ordinary grammar, a recursive feature exists for a CWS. That is, a CWS may be built by linking other CWSs, as well as FWSs. Obviously, compatibility of the linked CWSs must exist. A CWS is built with a special graphical compiler that ensures compatibility. The compiler fully comprehends the operation of the line coded FWSs that are imbedded within the compiler's software and cannot be altered by an apps builder. Furthermore, the compiler is interactive and guides the apps builder to ensure that the CWS being built is also fully understood by the compiler. After being built, a CWS is placed within the compiler's library for future recursion Medical and business applications represent especially fruitful areas for CWSs. When the systems are linked with CWSs, Mobile heart monitors will use cellular terminals to communicate with hospital software, physicians' mobile terminal software, etc. without prior development coordination. By using CWSs delivery vehicles can skirt traffic jams by linking state trooper traffic reports, via cellular terminals, with the vehicle's GPS guidance systems. This paper describes the procedure for building a CWS to illustrate the attributes alluded to above. It also provides introductory insights of how these attributes are achieved.