Abstract: A “generic” switch messaging protocol is disclosed for message handling and switch supervision in conjunction with a number of switching engines, each of which is conversant with the generic messaging protocol, each switching engine also being conversant with a specific switch messaging protocol. An object oriented development system is also disclosed utilizing a “generic” switch messaging protocol and a plurality of switching engines, each of which is conversant with the generic messaging protocol and each of which is conversant with a specific switch messaging protocol. Certain switch messages are not “genericized” because their functionality is different from the functionality of other switches. These messages generally include initialization and maintenance messages which are hardware specific and have no counterpart in another switch from a different vendor.

Abstract: An object-oriented over-the-air service provisioning (OTASP) computer program is disclosed. The OTASP program is implemented in a client-server architecture, wherein a plurality of client programs operating, on client platforms in a customer service centers, optionally in diverse geographical locations, communicate with the OTASP computer program. The OTASP computer program communicates with one or more mobile switching centers (MSC's) to process requests from the client programs and to request communication with mobile telephones using an over-the-air interface, in order to accomplish over-the-air service provisioning.

Abstract: A short message server (SMS) is provided with memory for storing short messages, and a SMS gateway/interworking (processing) block. The SMS accepts all properly formatted incoming messages, and queries an HLR database for destination information as well as to determine whether the destination of each incoming message is valid and authorized. If the destination is either not valid or not authorized, the SMS sends an error message to the originator, and effectively deletes the message from its memory. Where the destination is valid and authorized, the message is forwarded towards its destination. The SMS specifically does not include a subscriber database, and instead relies on the communication with the HLR and its subscriber database to provide the necessary information. Communication between the SMS and the HLR is preferably via the GSM MAP (mobile application part) protocol.

Abstract: A transaction handling system (THS) for use in a cellular telephone network using Short Messages is described. The THS comprises means for receiving digitally encoded information from one or more sources, such as magnetically encoded credit card information related to credit cards, smart cards, bar codes etc. Means are provided for interpreting the digitally encoded information into a message compatible with a particular database relevant in the transaction and formulating a query to the database. The query is routed to the database. Upon receiving a reply from the database, the reply is interpreted in the THS for compatibility with the cellular network and the structure of the Short Messages within it, and routed to a terminal having a display, printer or other input/output means.