[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

US6078820A - Real-time SMS application messaging using an SMSC-linked server - Google Patents

Real-time SMS application messaging using an SMSC-linked server Download PDF

Info

Publication number
US6078820A
US6078820A US09/347,756 US34775699A US6078820A US 6078820 A US6078820 A US 6078820A US 34775699 A US34775699 A US 34775699A US 6078820 A US6078820 A US 6078820A
Authority
US
United States
Prior art keywords
application
mobile station
sms message
message
format
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US09/347,756
Inventor
Mark Wells
Rolf Huber
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Oyj
Original Assignee
Nokia Mobile Phones Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Mobile Phones Ltd filed Critical Nokia Mobile Phones Ltd
Priority to US09/347,756 priority Critical patent/US6078820A/en
Application granted granted Critical
Publication of US6078820A publication Critical patent/US6078820A/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12Messaging; Mailboxes; Announcements
    • H04W4/14Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72436User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. short messaging services [SMS] or e-mails
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices

Definitions

  • This invention relates generally to wireless communicators and, in particular, to mobile stations such as those capable of operation with a cellular network.
  • SMS Short Message Service
  • the Short Message Service is a teleservice which enables a user to send messages to and receive text messages from other users of a communications (cellular) network.
  • the SMS function attempts to deliver a message to a mobile station whenever the mobile station is registered to the network, even when the terminal is engaged in a voice or data call.
  • the mobile station may also roam throughout the network and still be capable of sending and receiving messages.
  • a mobile station configured for SMS provides methods for the user to receive, read, write/edit, clear, send, and save messages.
  • the network stores messages in at least one SMS Center (SMSC), and Mobile Terminated (MT) messages are sent to the terminal from the SMSC.
  • SMSC SMS Center
  • MT Mobile Terminated
  • Various SMS protocol layers receive the messages and check their contents. If the contents are valid, and assuming that there is room for incoming text messages in the memory of the mobile station, the message is received and stored. Otherwise, the message is rejected.
  • SMS messages may be sent from an application resident in a mobile station, or from a PC application that is connected by a LAN to the internet.
  • a SMSC Short Message Service Center
  • the SMSC then immediately directs the message to the mobile station, or after it has detected that the mobile station has locked onto a channel and entered an idle state.
  • a further problem relates to the running of real-time applications from easily disconnected PCs, such as laptops, that may be occasionally disconnected from the normal host network. Information may need to be exchanged in a timely manner in either direction between the mobile station and the PC, yet the PC may be disconnected or the network may be too slow in delivering the data. In this case those applications which need to deliver or receive data messages, regardless of connection state and other circumstances, will not perform correctly.
  • the formats that have been specified thus far do not meet the high requirements imposed by a real-time SMS application messaging system.
  • the information is encoded in binary form which is not interpretable by humans, and/or the encoded information is too lengthy to be transmitted as a length-constrained SMS message, and/or the format is too specific to be used by a wide range of different applications.
  • the encoded information should be readable by a human (i.e., no binary encoding), should be easy for a user to enter, should be capable of being transmitted as a SMS message, should be as short as possible (preferably not exceeding the length of one SMS message), should consist only of characters which are supported by the SMS character set, and should be designed so that it can be stored without information conversion.
  • the message format should provide a mechanism which enables the encoded information to be divided and reassembled (in case the information exceeds the length of one SMS message), should allow a capability to define commands, and should not restrict its usage to one or more specific applications so as to preclude its use with future applications.
  • the message format should also be capable of holding one or more data values and should not restrict the order of data values, should allow parts of data values to be omitted, should provide an error handling capability, and should be sufficiently specified so that applications can represent any received encoded information in a user-friendly manner, even though a particular message was not intended for the user.
  • a method of this invention for operating a wireless mobile or user station to provide for real-time Short Message Service (SMS) Application Messaging, using an SMSC-linked server, for providing timely message delivery in non-deterministic networks and where device connections are intermittent or periodic.
  • SMS Short Message Service
  • Potential applications of this invention include, but are not limited to, using SMS-based messaging between groups of mobile stations and PCs for queued and scheduled email; for meeting, appointment and absence management; for obtaining reminders from organizer and calendar applications; for project hours reporting; for sales and inventory updating; for personalized information services; and for home security applications.
  • the method includes the steps of: (a) providing a database that is bidirectionally coupled to the user messaging function; (b) at the mobile station, entering information that is descriptive of an event, typically a future event; (c) sending the entered information from the mobile station to the database, via a message sent through the BMI and the user messaging function; and (d) storing the information in the database.
  • a method for operating a wireless mobile station of a type that is capable of bidirectional communication with a BMI having a SMS center.
  • the method includes the steps of: (a) receiving a SMS message from the BMI; (b) determining if the SMS message has a first transfer format or a second transfer format; (c) if the SMS message is determined to have the first transfer format, processing the SMS message in a conventional manner; (d) if the SMS message is determined to have the second transfer format, parsing the SMS message to locate an Application Identifier entry; (e) determining from the Application Identifier entry if the mobile station supports the identified application; (f) if not, displaying a data entry of the SMS message with a first display format; else, (g) if the mobile station does support the identified application, starting the application and displaying the data entry with a second display format specified by the application.
  • the second transfer format is a Data Exchange, Storage, and Command (DESC) format.
  • the SMS message is encoded to identify an event that was previously stored in a database that is coupled to the SMS center, and the SMS message is sent to the mobile station at a time specified in the database.
  • the information specifying the event was previously stored in the database in response to a SMS message that was originated by the mobile station, while in another embodiment the information specifying the event was previously stored in the database in response to a message that was originated by a data processor coupled to the database through a network, such as the internet.
  • the SMS message can be encoded to identify a prioritized future event that was previously stored in the database, and the SMS message is sent to the mobile station in response to a query from the mobile station to display all stored future events having a specified priority level.
  • the SMS message can be sent in response to a query from the mobile station to display all stored future events having a specified future date.
  • FIG. 1 is a block diagram of a mobile station that is suitable for use with this invention
  • FIG. 2 is an elevational view of the mobile station shown in FIG. 1, and which further illustrates a first embodiment of a cellular communication system to which the mobile station is bidirectionally coupled through wireless RF links;
  • FIG. 3 illustrates a second embodiment of a cellular communication system to which the mobile station is bidirectionally coupled through wireless RF links;
  • FIG. 4 is a logic flow diagram that illustrates a response of the mobile station to the receipt of a SMS message.
  • FIGS. 1, 2 and 3 for illustrating a wireless user terminal or mobile station 10, such as but not limited to a cellular radiotelephone or a personal communicator, that is suitable for practicing this invention.
  • the mobile station 10 includes an antenna 12 for transmitting signals to and for receiving signals from a base site or base station 30.
  • the base station 30 is a part of a cellular network comprising a Base Station/Mobile Switching Center/Interworking function (BMI) 32 that includes a mobile switching center (MSC) 34.
  • BMI Base Station/Mobile Switching Center/Interworking function
  • MSC 34 provides a connection to landline trunks, typically the Public Switched Telephone Network (PSTN) 38, when the mobile station 10 is involved in a call.
  • PSTN Public Switched Telephone Network
  • the mobile station includes a modulator (MOD) 14A, a transmitter 14, a receiver 16, a demodulator (DEMOD) 16A, and a controller 18 that provides signals to and receives signals from the transmitter 14 and receiver 16, respectively.
  • These signals include signalling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data.
  • the air interface standard is assumed for this invention to include a physical and logical frame structure suitable for the transmission of data and messages, including SMS or equivalent messaging facilities.
  • the controller 18 also includes the circuitry required for implementing the audio and logic functions of the mobile station.
  • the controller 18 may be comprised of a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and other support circuits. The control and signal processing functions of the mobile station are allocated between these devices according to their respective capabilities.
  • a user interface includes a conventional earphone or speaker 17, a conventional microphone 19, a display 20, and a user input device, typically a keypad 22, all of which are coupled to the controller 18.
  • the keypad 22 includes the conventional numeric (0-9) and related keys (#,*) 22a, and other keys 22b used for operating the mobile station 10. These other keys 22b may include, by example, a SEND key, various menu scrolling and soft keys, and a PWR key.
  • the mobile station 10 also includes a battery 26 for powering the various circuits that are required to operate the mobile station.
  • the mobile station 10 also includes various memories, shown collectively as the memory 24, wherein are stored a plurality of constants and variables that are used by the controller 18 during the operation of the mobile station.
  • the memory 24 stores the values of various cellular system parameters and the number assignment module (NAM).
  • NAM number assignment module
  • An operating program for controlling the operation of controller 18 is also stored in the memory 24 (typically in a ROM device).
  • the memory 24 may also store data, including user messages and SMS messages, that are received from the BMI 32 prior to the display of the messages to the user.
  • the mobile station 10 can be a vehicle mounted or a handheld device. It should further be appreciated that the mobile station 10 can be capable of operating with one or more air interface standards, modulation types, and access types. By example, the mobile station may be capable of operating with any of a number of air interface standards including IS-136, GSM and IS-95. It should thus be clear that the teaching of this invention is not to be construed to be limited to any one particular type of mobile station or air interface standard.
  • the operating program in the memory 24 includes routines to present messages and message-related functions to the user on the display 20, typically as various menu items.
  • the memory 24 also includes routines for implementing the methods described below.
  • a subscriber messaging function embodied, preferably, as a Short Message Service Center (SMSC) 36 that is coupled to the MSC 34.
  • the SMSC 36 is responsible for managing the SMS functions of the cellular system.
  • a network block 40 Connected to the PSTN 38 is a network block 40, which may be the internet, a private leased link, or any suitable wide-area or global communications network that is accessible from personal computers (PCs) 44.
  • the network 40 may operate with a TCP/IP protocol. Suitable, but not limiting, lower level protocols include X.25 and X.400.
  • Various Local Area Networks (LANs) 46 may also be connected to the network 40, providing access to the network 40 for LAN-connected PCs (not shown).
  • the system further includes a network server, such as a World Wide Web (WWW) server 42, that is coupled to the network 40.
  • WWW World Wide Web
  • the WWW server 42 implements a Personal Messaging Calendar (PMC) application.
  • PMC Personal Messaging Calendar
  • a direct connection is made from the WWW server 42 to the SMSC 36, while in the embodiment of FIG. 3 a port of the SMSC 36 is connected to the network 40.
  • a user typically a cellular subscriber, has access to the mobile station 10 and the PC 44 (having the connection to the network 40).
  • a suitable software program is loaded onto the PC 44 for implementing, by example, the PC-end of the PMC application.
  • the system operator has the WWW server 42 connected to the system operator's SMSC 36, as in FIG. 2, or connected to the network 40 as in FIG. 3.
  • the WWW server 42 has software designed to support the subscriber's PMC software.
  • the subscriber may also have PMC software, or firmware 24a, stored in the memory 24 of the mobile station 10. This software or firmware 24a is used to interact with SMS-based messaging applications, such as the PMC.
  • An example of a possible application of the invention is a reminder delivery system using the PMC application, wherein the subscriber instructs, from the mobile station 10 or the PC 42, to have a message delivered to his or her mobile station 10 at a predetermined time prior to a scheduled appointment.
  • the PC 44 may immediately update the WWW server 42 with the new calendar information, or it may wait until it is connected.
  • the WWW server 42 replicates the reminder delivery information so that the information is delivered on time through the latency-free cellular network, using the SMSC 36, MSC 34, BS 30, and the radio link to the mobile station 10.
  • the meeting reminder is delivered to the mobile station 10 using the SMS facility of the cellular network.
  • the subscriber may also use the mobile station 10 to send appointment or reminder information (e.g., a "To Do" list) to the PMC application running on the WWW server 42, using the mobile station's display 20, keypad 22, and the PMC firmware 24a stored in the memory 24.
  • appointment or reminder information e.g., a "To Do" list
  • the subscriber may also later review, cancel and modify the stored information in a similar manner, or may perform this function from the PC 44.
  • the WWW server 42 can be polled on a regular basis, by the subscriber's PC 44, to keep a current copy of the set of calendar appointment entries.
  • the WWW server 42 uses a predetermined protocol to communicate messages and their associated information to the SMSC 36, in a direct private connection over a low-latency communication link 42a. It should be realized that the SMSC 36 and WWW server 42 can be co-located at one site in the network provider's infrastructure, or may be separated by a considerable distance.
  • the WWW server 42 uses a specialized or proprietary protocol, that may be built upon a TCP/IP internet transfer layer, to communicate with the SMSC 36 via the network 40.
  • the PMC/WWW server 42 includes a subscriber database 43a and a real-time clock (time and date) function 43b.
  • the database 43a stores, by example, Appointment and "To Do" lists that were previously entered by the subscriber from one of the mobile station 10 or PC 44.
  • the exemplary PC application is referred to as the Personal Messaging Calendar (PMC), or simply as the Messaging Calendar (MC), and the WWW server 42 may be referred to also as the Personal Message Center (PMC).
  • PMC Personal Messaging Calendar
  • MC Messaging Calendar
  • WWW server 42 may be referred to also as the Personal Message Center (PMC).
  • PMC Personal Messaging Calendar
  • MC Messaging Calendar
  • PMC Personal Message Center
  • the PMC application and database 43a running on the WWW server 42 functions as a master information holder for applications such as the Messaging Calendar. Since the PMC/WWW server 42 is accessible by the network 40 and the PSTN 38, it is configured with a suitable interface, such as the WWW-based subscriber interface that can be accessed with a conventional internet browser program. This implies that the subscriber can access his or her calendar entries and reminders from anywhere in the world through the network 40, a telephone network, or any other means of reaching the PSTN 38.
  • the PMC application having access to the SMSC 36 through the link 42a (FIG. 2) or the network 40 (FIG.
  • 3 is additionally capable of recording all of the subscriber's transmitted and received SMS messages, and for also maintaining a record as to whether transmitted SMS messages have reached their destination.
  • Subscriber groups and standard message storage are available from the WWW-based PMC, so that the subscriber may directly send messages.
  • the PC 44 portion of the PMC application 44a may run under any suitable PC operating system, including those that present applications in windows.
  • the subscriber is able to rely on appointments and reminders being sent to his or her mobile station 10 in a timely manner.
  • the mobile station 10 does not need to be connected by cable to the PC 44. Instead, the reminders can sent automatically from the network-connected PC 42, through the network 40 and PMC/WWW server 42, to the SMSC 36.
  • the SMSC 36 then formats a suitable SMS message, either in accordance with the SMS signalling protocol of the applicable air interface standard or a presently preferred DESC format (described below), and causes the SMS message to be transmitted to the mobile station 10 through the MSC 34 and BS 30. Appointment, message and timely reminder texts can thus be sent from the desktop PC 44 to the subscriber's mobile station display 20.
  • the PMC/WWW server 42 For those times when the subscriber does not have access to the mobile station 10, and wishes to view and possibly respond to new messages, access is made to the PMC/WWW server 42. This access can be made through the network 40 from the PC 44 or a LAN-connected PC.
  • the subscriber has immediate access, from anywhere in the world, to the PMC application with the WWW browser-equipped PC 44, personal digital assistant (PDA) device, or any suitable data processor capable of accessing the network 40.
  • PDA personal digital assistant
  • the subscriber simply accesses the PMC application running at the PMC/WWW server 42 as he or she would any internet site. After the correct identification is made, the subscriber has access to the subscriber's messages and other information maintained by the PMC application running at the PMC/WWW server 42.
  • one or more new calendar appointments may be entered by the subscriber directly into a window on the PC 44, or previous appointments may be reviewed, deleted, or revised, and the appointment or appointments are transferred automatically from the subscriber's PC-based calendar application that is running on the PC 44 to the PMC/WWW Server 42. For example, this could be done in the morning before the subscriber leaves the home or the office to make, for example, sales calls.
  • a reminder Prior to each scheduled appointment a reminder is sent to the subscriber's mobile phone display 20, via the SMSC 36, MSC 34 and BS 30.
  • the appointment reminder is received by mobile station 10 as a SMS message (preferably a DESC-encoded SMS message as described below), and is stored in the memory 24 for review by the subscriber, using the normal SMS message capabilities of the mobile station 10.
  • the Personal Messaging Calendar application also enables immediate SMS messaging from the PC 44 to the mobile station 10.
  • An acknowledgment of receipt of the SMS messages by the mobile station 10 is also supported.
  • a call-back number and reply charge-acceptance may also be selected on a per message basis.
  • a Messaging Window of the Personal Messaging Calendar application running at the PC 44 accepts the appointment entries and messages into a graphical representation of the mobile station's display 20. That is, the subscriber may be presented with a similar user interface whether accessing the PMC application from the PC 44 or the mobile station 10. Basic editing functions may be performed within the display area. This allows the subscriber to enter the text as the subscriber wishes the text to be later displayed at the receiving mobile station 10.
  • the calendar entries can be selected to repeat at convenient intervals, and the subscriber is made aware of any scheduling conflicts entered into the calendar.
  • a Message Validity time-out is configurable for those messages that are time critical, or that will become outdated at a certain time.
  • the message reply destination is also configurable, with the default destination being the subscriber's cellular phone number.
  • a warning is displayed if a message is sent when the SMSC 36 is not functioning.
  • a confirmation is displayed when some number of re-try attempts finally achieve successful delivery.
  • any SMS Messages sent to the subscriber's mobile station 10 from other mobile subscribers may be copied to the PMC/WWW server 42 by the SMSC 36.
  • the subscriber may add, edit, delete or send any message while in the PMC application running on the PMC/WWW server 42.
  • Messages that have successfully reached the mobile station 10 are flagged so that only unread messages may be conveniently selected. Messages already read are moved from an ⁇ unread ⁇ or new message folder to an ⁇ old ⁇ message folder.
  • the subscriber may also originate messages from the Personal Message Center application.
  • the messages may be sent to individuals or to groups.
  • the PMC application supports a list of possible messages, stored in folders, that may be selected to facilitate message origination.
  • the subscriber may also create and store a list of phone numbers by parsing stored call-back numbers. Group mailing lists may be formed from the list of phone numbers in the PMC, which can be automatically updated by the PMC.
  • the Personal Message Center application is the management of the timed release of outgoing reminders and messages.
  • the subscriber may add, edit, or delete messages while connected to the PMC application. All messages are preferably encrypted in order to pass securely through the network 40, such as the internet, to the Personal Message Center application running on the PMC/WWW server 42, and from the PMC/WWW server 42 to the SMSC 36 via the network 40 (as in the embodiment of FIG. 3).
  • the data set holds all the information which is needed by an application. This includes the data set's identification, additional information for the application, and the actual data items.
  • the data set can be thought of as one unit which can be stored in a memory, exchanged among different applications, or sent from or received by the mobile station 10 via the air interface.
  • a data set can have the appearance of a string, a SMS message, or any other structure that can accommodate ASCII characters.
  • ASCII characters refer to the standard character set of the applicable air interface standard (e.g., GSM or IS-136).
  • a data set can be of arbitrary length. In practice, however, the actual length is constrained by the data set's appearance. It may happen that the length of the information exceeds the length of a data set. In this case the information must be broken down into two or more data sets.
  • the DESC format provides a mechanism to handle these situations, as will be described below.
  • the first two characters of a data set are two forward slashes //. These two slashes indicate that the remainder of the information is DESC-format encoded.
  • the end of a data set is not specified, as it varies depending on the data set's appearance. For example, the end of a data set implemented in the C programming language is indicated by a ⁇ 0 ⁇ (zero terminated string).
  • the generic DESC format of a data set is: // ⁇ remainder of the information>.
  • the ⁇ remainder of the information> consists of fields or entries.
  • An entry holds all relevant information for one data item.
  • Entries are separated from one other with a comma (,) delimiter.
  • a given entry has three parts: the entry identifier, the entry options, and the entry value.
  • the identifier, options and value parts are separated from each other with a colon (:) delimiter.
  • the order of the entry parts is fixed as: identifier, options, value.
  • the application entry contains important information for the application which must process the information that follows after the application entry. There is always one, and only one, application entry in the data set. It is always the first entry.
  • the three parts of an application entry are referred to as the application identifier, the application option, and the application value.
  • a given application entry must have one application identifier, can have none, one, or several application options, and can have one application value.
  • An application identifier is the first part of an application entry. It names the application to which the data set is being sent. However, other applications may be able to interpret the data set if the data set contains common data identifiers.
  • the application options give additional information to the destination application about the remainder of the DESC encoded information.
  • An application entry may include none, one or several application options.
  • An application value describes the type of the encoded information. The application value is not mandatory, and can be eliminated. However, if used only predefined application values are legal.
  • a data entry holds the actual data that the destination application is to work with. There can be none, one, or several data entries in a data set, and the data entries always follow after the application entry.
  • the three parts of a data entry are referred to as the data identifier, the data option, and the data value.
  • a given data entry must have one data identifier, can have no data option or can have several data options (if there is a data value), and can have one data value.
  • the data identifier is the first part of a data entry. It is a description for the value of the corresponding data entry. Data options are defined so as to give additional information about the data value. In practice, data options may be infrequently used, and are therefore application specific. Every application may define its own data options. A data entry may include none, one or several data options. The data value is the actual data which is referred to by the data identifier within the same data entry.
  • a data value can consist of any sequence of letters, digits, blank spaces and punctuation marks. Commas (,) and colons (:) are handled differently.
  • An identifier consists of one letter or a sequence of letters and underscores. No blanks or white spaces are allowed. At least the first character of an identifier must be a letter. Identifiers are not case sensitive. There is no limitation in length for identifiers, but for practical purposes they are kept as short as possible.
  • An option is split into several parts: the option identifier, the option argument, and the option value.
  • the option identifier, option argument and option value build one sequence of characters. No blanks or white spaces are allowed.
  • the option value is defined as zero (0) or any positive integer.
  • Preliminary, predefined DESC identifiers and possible options are intended for applications, such as the PMC application described above, which use them for value references. For that reason, application and data identifiers are defined only in English.
  • This option requests the receiver of the message to confirm the reception of the encoded information.
  • the form of the confirmation is a function of the application.
  • the data set can be given a unique identification.
  • y can be 0 or any positive integer
  • the present data set can be marked as the mth part out of n parts in total.
  • the values of m and n can be any positive integer. It is the application's responsibility to split and concatenate the parts of the data set in a correct manner. This option is used when it is impossible to pack the information to be sent within one data set.
  • the above-described ID option can be used in connection with the PART option.
  • the PART option is especially useful when a PMC message or reminder exceeds the maximum length allocated for a SMS message in the Cellular system illustrated in FIGS. 2 and 3.
  • This option indicates the version number of the application (e.g., PMC Ver. 1.0 or PMC Ver. 1.1) which has created the present data set.
  • the variable x can be 0 or any positive integer.
  • the application value (value of the first entry of a data set) is reserved for application specific information. By not supplying any application value indicates the "standard information" of the application that is identified by the application identifier.
  • the ERROR application value can be used by any application to indicate a fault in message processing.
  • the DESC specification does not define the contents of the data set for an error message. However, one of at least two generic formats can be followed.
  • a message with a COMMAND application value is constructed freely according to a conventional, generic format and an application's need.
  • a command is usually sent to a specific application, such as the PMC application. However, several applications may use same command entry.
  • a command can be applied specifically to a certain message or data set without specifying additional command options or command values. For example:
  • the REPLY application value can be used to identify the data set as an answer or a reply to a request or a command.
  • the format is as follows:
  • the QUERY application value can be used if an application is to retrieve certain information from another application.
  • Search criterion are given by specifying one or more data entries. If there is more than one data entry, they are ANDed for the search.
  • a number of the foregoing Data Identifiers are used by the PMC application software, including MSG, DATE, TIME, ETIME, and ADATE.
  • the above described DESC format thus specifies a way to encode information. Encoded information can be sent as short messages (e.g., SMS messages) to or from the mobile station 10. Any information that is encoded in DESC format can be stored in a memory or processed as any other character string, since it consists only of ASCII characters.
  • a DESC Message Parsing option is selected from a displayed feature list.
  • the mobile station 10 is able to recognize, then parse, DESC messages and display the result on the display 20.
  • the mobile station's software must have a priori knowledge of the structure of the DESC message format.
  • the mobile station 10 is not required to process the received data.
  • an application or data identifier is not known to the mobile stations's software (for example, is not stored in a list of supported applications), then the application identifier or data identifier and the associated data value is shown "as is". However, if an application or data identifier is known to the software, it being assumed that the software maintains a pre-programmed list, which can be extended by sending another DESC message, then the application identifier or data identifier and its associated data value are translated and displayed in a more convenient, application specific format.
  • the procedure that is applied to displaying the DESC message need not differ from the procedure used for conventional SMS message handling.
  • the application specific information that is displayed includes the application identifier and application value.
  • the data specific information that is displayed consists of the data identifier and data value.
  • the mobile station 10 may be displayed in a first display format as follows, when parsing is performed by the mobile station 10 (assuming that all identifiers are unknown, and DESC Message Parsing is selected from a displayed feature list):
  • DESC message may be shown as follows when parsed and suitably translated, where translation presupposes that both DESC Message Parsing and a PMC-related Calendar Translator Application are selected from the displayed feature list:
  • Calendar Translator application has translated the abbreviated application and data identifiers into full words (English in this case, although any language (user selected) may be supported). Also, dates and times have been formatted in a local manner. Also, the end date information is optionally deleted, as the end date is equal to the start date. As such, the message is displayed in a second display format that differs significantly from the first display format.
  • Each application that may be parsed with the DESC Message Parsing feature have their own associated translation and executable features that may be selected from the user interface feature list.
  • translator and execution features may be loaded into the mobile station 10, using the DESC format via SMS.
  • the mobile station 10 receives a SMS message.
  • the mobile station 10 determines if the SMS message is in a first transfer format or a second transfer format. That is, it is determined if the SMS message is in a non-DESC format or the DESC format (as described above). If not in the DESC format, control passes to Block C to perform conventional SMS processing. If the received SMS message is in the DESC format control instead passes to Block D where the controller 18, operating under the control of DESC-related firmware or software, parses the DESC encoded SMS message.
  • Block E a determination is made if the Application Identifier is a known (to the mobile station) application identifier.
  • the application identifier is the first part of an application entry, and it names the application to which the data set is being sent. If the Application Identifier is known, control passes to Block F where the associated application (e.g., APP or appointments) is initiated (see the example presented above relating to the Lunch message). If the Application Identifier is not known (to the mobile station 10), control passes instead to Block G where the associated text message is presented without the application-specific formatting.
  • the associated application e.g., APP or appointments
  • a subscriber having the mobile station 10 is enabled to access a desired application using a displayed menu. After selecting the desired application the subscriber may manipulate soft keys and the keypad 22 so as to enter information in response to prompts (assuming that the mobile station does not include a touch screen or some other suitable user interface). By example, to enter an appointment into the PMC application, the following display may be presented.
  • TEXT A description for the appointment (e.g., Lunch with Jim, the location of the restaurant, etc.).
  • START INFO The subscriber enters the starting date and time for the appointment.
  • ALERT INFO The subscriber enters an alert date and time for the appointment (e.g., one hour prior to the Start time).
  • a SAVE soft key can be depressed. Depressing the SAVE soft key initiates sending the entered information to the PMC/WWW server 42.
  • the appointment information is sent to the PMC/WWW server 42 using a DESC-encoded SMS message, via the RF link, BS 30, MSC 34, SMSC 36, and one of the link 42a or the network 40.
  • the PMC/WWW server 42 initiates the sending of a DESC-encoded SMS message to the mobile station 10, via a path that is the reverse of that used to send the appointment information to the PMC/WWW server 42.
  • a message receipt confirmation message back to the mobile station 10 from the PMC/WWW server 42.
  • the mobile station 10 displays a suitable message (e.g., ⁇ Appointment Saved ⁇ ) along with the Appointment Title.
  • a suitable message e.g., ⁇ Appointment Saved ⁇
  • a SMS message is sent to the mobile station 10.
  • One suitable displayed message format is to display the text "Reminder", along with the text "At” followed by the Time of the appointment, if the time was saved with the appointment.
  • the subscriber may also interact with the display 20 and keypad 22 to view existing appointments for a particular date.
  • the mobile station 10 sends a SMS message to the PMC/WWW server 42, after prompting the subscriber to enter the date of interest.
  • a message "Appointments Received" can be displayed. Thereafter the subscriber can scroll through the appointments that were previously saved for the date of interest, which may be displayed by Title.
  • Similar or identical functionality is available from the PC 44, thereby providing the subscriber with multiple ways to access the information, while providing a unified and self-consistent user interface.
  • the subscriber is also enabled to instead enter a "To Do" reminder or event.
  • a "To Do" into the PMC application the following display may be presented.
  • a SAVE soft key can be depressed. Depressing the SAVE soft key initiates sending the entered information to the PMC/WWW server 42.
  • the "To Do" information is sent to the PMC/WWW server 42 using a DESC-encoded SMS message, via the RF link, BS 30, MSC 34, SMSC 36, and one of the link 42a or the network 40.
  • the subscriber may also interact with the display 20 and keypad 22 to view, delete, and edit existing "To Do” entries.
  • the subscriber may select to view all "To Do” entries in the list, or to view only those "To Do” entries having a specified priority class or level.
  • the mobile station 10 sends a SMS message to the PMC/WWW server 42, after prompting the subscriber to enter the desired priority class.
  • a message "To Do List Received" can be displayed. Thereafter the subscriber can scroll through the "To Do" entries that were previously saved for the desired priority class.
  • the subscriber can also interact with the display 20 and keypad 22 to delete and revise previously saved Appointment and "To Do" entries. Also, and as was described above, the subscriber can also gain access to the subscriber's database 43a entries in the PMC/WWW server 42 via the PMC software installed in the PC 44. In this manner various Appointment and "To Do" entries can be entered, saved, reviewed and modified from the PC 44. In both cases (e.g., mobile station access or PC access), the presently preferred DESC format is used (with any suitable modifications that may be required in order to pass through the network 40). Also in both cases, the subscriber is enabled to store information relating to some event, typically a future event, in the database 43a that is coupled to the messaging function or SMSC 36.
  • a subscriber can be notified of the receipt of email by storing the notification and/or the email header information into the database 43a. This can be done from a data processor that functions as an email server 48. In this example the Alert time could be set to zero. That is, subscriber-related information and events can be stored in the database 43a by other than the subscriber or the SMSC 36, in this case by the email server 48.
  • a non-volatile portion 24b of the memory 24 is allocated for local storage (LS).
  • the local storage 24b may be allocated either statically or dynamically.
  • the local storage 24b can be used to store the user's events to be viewed immediately or when out of a cellular coverage area.
  • the local storage 24b can also be used to temporarily store added or modified user events when out of the cellular coverage area. After the mobile station 10 is once more in a cellular coverage area the stored events can be transmitted to the PMC/WWW Server 42 using the protocols described above.
  • the user can also employ the local storage 24b to temporarily store events should the user decide to postpone a reply action for a received alert.
  • the local storage 24b also provides a mechanism to generate locally triggered alerts. For example, the user stores an alert in the local storage 24b, which is then checked by local PMC application software 24a using an internal real-time clock (RTC) 21. An alert is then triggered locally when the current time matches the time stored with the alert in the local storage 24b. Both user-generated information and information received from the BMI 32 can be stored in the local storage 24b.
  • RTC real-time clock
  • This screen saver may function as any conventional password-protected screen saver, but in addition displays a floating or moving window. Using the window anyone visiting the user's PC site (such as an associate in the user's office) can enter a SMS message. After completing the message a predetermined keystroke or mouse click causes the entered SMS message to be transferred automatically to the user's mobile station 10 via the PMC/WWW Server 42 and SMSC 36.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Human Computer Interaction (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

A method is disclosed for operating a wireless mobile station of a type that is capable of bidirectional communication with a BMI having a SMS center. The method includes the steps of: (a) receiving a SMS message from the BMI; (b) determining if the SMS message has a first transfer format or a second transfer format; (c) if the SMS message is determined to have the first transfer format, processing the SMS message in a conventional manner; (d) if the SMS message is determined to have the second transfer format, parsing the SMS message to locate an Application Identifier entry; (e) determining from the Application Identifier entry if the mobile station supports the identified application; (f) if not, displaying a data entry of the SMS message with a first display format; else, (g) if the mobile station does support the identified application, starting the application and displaying the data entry with a second display format specified by the application. In a presently preferred embodiment of this invention the second format is a Data Exchange, Storage, and Command (DESC) format, and an application specified by the DESC formatted SMS message can be a Personal Messaging Calendar (PMC) application. Access to the PMC application can be via SMS messages from the mobile station, or through a network-connected data processor, such as a PC connected to the internet.

Description

This application is a Division of Ser. No. 08/811,550 filed Mar. 4, 1997.
CLAIM OF PRIORITY FROM A COPENDING PROVISIONAL APPLICATION
This patent application claims priority under 35 U.S.C. §1.119(e) from copending Provisional Patent Application No. 60/036,770, filed Jan. 31, 1997 with Express Mail Certificate No.: EM 029 037 951 US, entitled "REAL-TIME SMS APPLICATION MESSAGING USING AN SMSC-LINKED SERVER" by M. Wells and R. Huber, the disclosure of which is incorporated by reference herein in its entirety.
FIELD OF THE INVENTION
This invention relates generally to wireless communicators and, in particular, to mobile stations such as those capable of operation with a cellular network.
BACKGROUND OF THE INVENTION
The Short Message Service (SMS) is a teleservice which enables a user to send messages to and receive text messages from other users of a communications (cellular) network. The SMS function attempts to deliver a message to a mobile station whenever the mobile station is registered to the network, even when the terminal is engaged in a voice or data call. The mobile station may also roam throughout the network and still be capable of sending and receiving messages. A mobile station configured for SMS provides methods for the user to receive, read, write/edit, clear, send, and save messages.
The network stores messages in at least one SMS Center (SMSC), and Mobile Terminated (MT) messages are sent to the terminal from the SMSC. Various SMS protocol layers receive the messages and check their contents. If the contents are valid, and assuming that there is room for incoming text messages in the memory of the mobile station, the message is received and stored. Otherwise, the message is rejected.
Reference can be had to the TIA Interim Standards IS-136 and IS-137, and also to a document entitled "TDMA Forum, Implementation Guide: Short Message Terminals Compliant With IS-136 and IS-137" (Ed. D. Holmes, vers. 7.0, Apr. 20, 1995). These documents specify a type of SMS and the various system and terminal level protocols required to provide SMS in a cellular telecommunications system.
In current telecommunications systems SMS messages may be sent from an application resident in a mobile station, or from a PC application that is connected by a LAN to the internet. A SMSC (Short Message Service Center) receives the SMS message from the cellular network, or from an internet gateway, respectively. The SMSC then immediately directs the message to the mobile station, or after it has detected that the mobile station has locked onto a channel and entered an idle state.
A problem exists with this current approach, in that there may exist a set of PC applications that are designed to communicate with a user's own mobile station or other mobile stations. That is, applications currently exist or will exist that require a more deterministic delivery of information when using the internet.
A further problem relates to the running of real-time applications from easily disconnected PCs, such as laptops, that may be occasionally disconnected from the normal host network. Information may need to be exchanged in a timely manner in either direction between the mobile station and the PC, yet the PC may be disconnected or the network may be too slow in delivering the data. In this case those applications which need to deliver or receive data messages, regardless of connection state and other circumstances, will not perform correctly.
Furthermore, a number of different formats have been specified for encoding information to enable applications to communicate with one another. One application must be capable of interpreting information that has been generated and encoded by another application.
Unfortunately, the formats that have been specified thus far do not meet the high requirements imposed by a real-time SMS application messaging system. Typically the information is encoded in binary form which is not interpretable by humans, and/or the encoded information is too lengthy to be transmitted as a length-constrained SMS message, and/or the format is too specific to be used by a wide range of different applications.
Ideally, a flexible yet well defined generic format and message structure is needed which fulfills the following criteria.
First, the encoded information should be readable by a human (i.e., no binary encoding), should be easy for a user to enter, should be capable of being transmitted as a SMS message, should be as short as possible (preferably not exceeding the length of one SMS message), should consist only of characters which are supported by the SMS character set, and should be designed so that it can be stored without information conversion.
Second, the message format should provide a mechanism which enables the encoded information to be divided and reassembled (in case the information exceeds the length of one SMS message), should allow a capability to define commands, and should not restrict its usage to one or more specific applications so as to preclude its use with future applications. The message format should also be capable of holding one or more data values and should not restrict the order of data values, should allow parts of data values to be omitted, should provide an error handling capability, and should be sufficiently specified so that applications can represent any received encoded information in a user-friendly manner, even though a particular message was not intended for the user.
Also, most message formats are specified for "one-way" communication, meaning that information is sent from a sender to a receiver. They do not take into account possible responses, results of queries, or error handling on a high level.
OBJECTS OF THE INVENTION
It is thus a first object of this invention to provide an improved method for delivering messages in a telecommunications system.
It is another object of this invention to provide a telecommunications system having a wireless component, wherein SMS messages are used in the wireless component, and to enable applications to communicate through the system using SMS messages.
It is a further object of this invention to provide a generic message format which fulfills the requirements for a real-time SMS application messaging system.
SUMMARY OF THE INVENTION
The foregoing and other problems are overcome and the objects of the invention are realized by methods and apparatus in accordance with embodiments of this invention. A method of this invention is disclosed for operating a wireless mobile or user station to provide for real-time Short Message Service (SMS) Application Messaging, using an SMSC-linked server, for providing timely message delivery in non-deterministic networks and where device connections are intermittent or periodic.
By connecting the server directly to a SMSC, or by linking the server to the SMSC through a low latency network, applications can tolerate the latency and intermittence of the LAN-based PC link which is connected to a network, such as the internet or a private leased link. PC and mobile station-based applications are enabled to direct SMS messages to the server to achieve timely store-and-forward functionality.
Potential applications of this invention include, but are not limited to, using SMS-based messaging between groups of mobile stations and PCs for queued and scheduled email; for meeting, appointment and absence management; for obtaining reminders from organizer and calendar applications; for project hours reporting; for sales and inventory updating; for personalized information services; and for home security applications.
A method is disclosed for operating a wireless mobile station of a type that is capable of bidirectional communication with a Base Station, Mobile Switching Center, Interworking Function (BMI) having a user messaging function, such as a Short Message Service (SMS) function. The method includes the steps of: (a) providing a database that is bidirectionally coupled to the user messaging function; (b) at the mobile station, entering information that is descriptive of an event, typically a future event; (c) sending the entered information from the mobile station to the database, via a message sent through the BMI and the user messaging function; and (d) storing the information in the database.
Further in accordance with this invention a method is disclosed for operating a wireless mobile station of a type that is capable of bidirectional communication with a BMI having a SMS center. The method includes the steps of: (a) receiving a SMS message from the BMI; (b) determining if the SMS message has a first transfer format or a second transfer format; (c) if the SMS message is determined to have the first transfer format, processing the SMS message in a conventional manner; (d) if the SMS message is determined to have the second transfer format, parsing the SMS message to locate an Application Identifier entry; (e) determining from the Application Identifier entry if the mobile station supports the identified application; (f) if not, displaying a data entry of the SMS message with a first display format; else, (g) if the mobile station does support the identified application, starting the application and displaying the data entry with a second display format specified by the application. In a presently preferred embodiment of this invention the second transfer format is a Data Exchange, Storage, and Command (DESC) format.
In an exemplary, but not limiting, embodiment of this invention the SMS message is encoded to identify an event that was previously stored in a database that is coupled to the SMS center, and the SMS message is sent to the mobile station at a time specified in the database. In one embodiment the information specifying the event was previously stored in the database in response to a SMS message that was originated by the mobile station, while in another embodiment the information specifying the event was previously stored in the database in response to a message that was originated by a data processor coupled to the database through a network, such as the internet.
In the exemplary embodiment the SMS message can be encoded to identify a prioritized future event that was previously stored in the database, and the SMS message is sent to the mobile station in response to a query from the mobile station to display all stored future events having a specified priority level.
Also in the exemplary embodiment the SMS message can be sent in response to a query from the mobile station to display all stored future events having a specified future date.
BRIEF DESCRIPTION OF THE DRAWINGS
The above set forth and other features of the invention are made more apparent in the ensuing Detailed Description of the Invention when read in conjunction with the attached Drawings, wherein:
FIG. 1 is a block diagram of a mobile station that is suitable for use with this invention;
FIG. 2 is an elevational view of the mobile station shown in FIG. 1, and which further illustrates a first embodiment of a cellular communication system to which the mobile station is bidirectionally coupled through wireless RF links;
FIG. 3 illustrates a second embodiment of a cellular communication system to which the mobile station is bidirectionally coupled through wireless RF links; and
FIG. 4 is a logic flow diagram that illustrates a response of the mobile station to the receipt of a SMS message.
DETAILED DESCRIPTION OF THE INVENTION
Reference is made to FIGS. 1, 2 and 3 for illustrating a wireless user terminal or mobile station 10, such as but not limited to a cellular radiotelephone or a personal communicator, that is suitable for practicing this invention. The mobile station 10 includes an antenna 12 for transmitting signals to and for receiving signals from a base site or base station 30. The base station 30 is a part of a cellular network comprising a Base Station/Mobile Switching Center/Interworking function (BMI) 32 that includes a mobile switching center (MSC) 34. The MSC 34 provides a connection to landline trunks, typically the Public Switched Telephone Network (PSTN) 38, when the mobile station 10 is involved in a call.
The mobile station includes a modulator (MOD) 14A, a transmitter 14, a receiver 16, a demodulator (DEMOD) 16A, and a controller 18 that provides signals to and receives signals from the transmitter 14 and receiver 16, respectively. These signals include signalling information in accordance with the air interface standard of the applicable cellular system, and also user speech and/or user generated data. The air interface standard is assumed for this invention to include a physical and logical frame structure suitable for the transmission of data and messages, including SMS or equivalent messaging facilities.
It is understood that the controller 18 also includes the circuitry required for implementing the audio and logic functions of the mobile station. By example, the controller 18 may be comprised of a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and other support circuits. The control and signal processing functions of the mobile station are allocated between these devices according to their respective capabilities.
A user interface includes a conventional earphone or speaker 17, a conventional microphone 19, a display 20, and a user input device, typically a keypad 22, all of which are coupled to the controller 18. The keypad 22 includes the conventional numeric (0-9) and related keys (#,*) 22a, and other keys 22b used for operating the mobile station 10. These other keys 22b may include, by example, a SEND key, various menu scrolling and soft keys, and a PWR key. The mobile station 10 also includes a battery 26 for powering the various circuits that are required to operate the mobile station.
The mobile station 10 also includes various memories, shown collectively as the memory 24, wherein are stored a plurality of constants and variables that are used by the controller 18 during the operation of the mobile station. For example, the memory 24 stores the values of various cellular system parameters and the number assignment module (NAM). An operating program for controlling the operation of controller 18 is also stored in the memory 24 (typically in a ROM device). The memory 24 may also store data, including user messages and SMS messages, that are received from the BMI 32 prior to the display of the messages to the user.
It should be understood that the mobile station 10 can be a vehicle mounted or a handheld device. It should further be appreciated that the mobile station 10 can be capable of operating with one or more air interface standards, modulation types, and access types. By example, the mobile station may be capable of operating with any of a number of air interface standards including IS-136, GSM and IS-95. It should thus be clear that the teaching of this invention is not to be construed to be limited to any one particular type of mobile station or air interface standard.
The operating program in the memory 24 includes routines to present messages and message-related functions to the user on the display 20, typically as various menu items. The memory 24 also includes routines for implementing the methods described below.
Referring specifically to FIGS. 2 and 3, there is also provided a subscriber messaging function embodied, preferably, as a Short Message Service Center (SMSC) 36 that is coupled to the MSC 34. The SMSC 36 is responsible for managing the SMS functions of the cellular system. Connected to the PSTN 38 is a network block 40, which may be the internet, a private leased link, or any suitable wide-area or global communications network that is accessible from personal computers (PCs) 44. The network 40 may operate with a TCP/IP protocol. Suitable, but not limiting, lower level protocols include X.25 and X.400. Various Local Area Networks (LANs) 46 may also be connected to the network 40, providing access to the network 40 for LAN-connected PCs (not shown).
In accordance with an aspect of this invention the system further includes a network server, such as a World Wide Web (WWW) server 42, that is coupled to the network 40. In the illustrated embodiments of this invention the WWW server 42 implements a Personal Messaging Calendar (PMC) application. Although the ensuing description will be made primarily in the context of the PMC application, it should be realized that the PMC application is exemplary of the wide-number of possible applications that can be implemented at the server 42, in accordance with the teachings of this invention.
In the embodiment of FIG. 2 a direct connection is made from the WWW server 42 to the SMSC 36, while in the embodiment of FIG. 3 a port of the SMSC 36 is connected to the network 40. The distinctions between these two embodiments will be made more apparent below.
In order to take advantage of the full functionality offered by this invention, a user, typically a cellular subscriber, has access to the mobile station 10 and the PC 44 (having the connection to the network 40). A suitable software program is loaded onto the PC 44 for implementing, by example, the PC-end of the PMC application. The system operator has the WWW server 42 connected to the system operator's SMSC 36, as in FIG. 2, or connected to the network 40 as in FIG. 3. The WWW server 42 has software designed to support the subscriber's PMC software. The subscriber may also have PMC software, or firmware 24a, stored in the memory 24 of the mobile station 10. This software or firmware 24a is used to interact with SMS-based messaging applications, such as the PMC.
An example of a possible application of the invention is a reminder delivery system using the PMC application, wherein the subscriber instructs, from the mobile station 10 or the PC 42, to have a message delivered to his or her mobile station 10 at a predetermined time prior to a scheduled appointment. If the PC 44 is connected to the network 40, it may immediately update the WWW server 42 with the new calendar information, or it may wait until it is connected. The WWW server 42 replicates the reminder delivery information so that the information is delivered on time through the latency-free cellular network, using the SMSC 36, MSC 34, BS 30, and the radio link to the mobile station 10. The meeting reminder is delivered to the mobile station 10 using the SMS facility of the cellular network.
The subscriber may also use the mobile station 10 to send appointment or reminder information (e.g., a "To Do" list) to the PMC application running on the WWW server 42, using the mobile station's display 20, keypad 22, and the PMC firmware 24a stored in the memory 24. The subscriber may also later review, cancel and modify the stored information in a similar manner, or may perform this function from the PC 44.
The WWW server 42 can be polled on a regular basis, by the subscriber's PC 44, to keep a current copy of the set of calendar appointment entries.
In FIG. 2 the WWW server 42 uses a predetermined protocol to communicate messages and their associated information to the SMSC 36, in a direct private connection over a low-latency communication link 42a. It should be realized that the SMSC 36 and WWW server 42 can be co-located at one site in the network provider's infrastructure, or may be separated by a considerable distance.
In FIG. 3, the WWW server 42 uses a specialized or proprietary protocol, that may be built upon a TCP/IP internet transfer layer, to communicate with the SMSC 36 via the network 40.
In both cases the PMC/WWW server 42 includes a subscriber database 43a and a real-time clock (time and date) function 43b. The database 43a stores, by example, Appointment and "To Do" lists that were previously entered by the subscriber from one of the mobile station 10 or PC 44.
In the examples of FIGS. 2 and 3 the exemplary PC application is referred to as the Personal Messaging Calendar (PMC), or simply as the Messaging Calendar (MC), and the WWW server 42 may be referred to also as the Personal Message Center (PMC). It should be realized that these functions are "personal" in so far as an individual subscriber is concerned. Typically, however, the PMC application software running at the PMC/WWW server 42 will be interacting with hundreds or thousands of subscribers, each having access to at least one of a mobile station 10 and a PC 44.
The PMC application and database 43a running on the WWW server 42 functions as a master information holder for applications such as the Messaging Calendar. Since the PMC/WWW server 42 is accessible by the network 40 and the PSTN 38, it is configured with a suitable interface, such as the WWW-based subscriber interface that can be accessed with a conventional internet browser program. This implies that the subscriber can access his or her calendar entries and reminders from anywhere in the world through the network 40, a telephone network, or any other means of reaching the PSTN 38. The PMC application, having access to the SMSC 36 through the link 42a (FIG. 2) or the network 40 (FIG. 3), is additionally capable of recording all of the subscriber's transmitted and received SMS messages, and for also maintaining a record as to whether transmitted SMS messages have reached their destination. Subscriber groups and standard message storage are available from the WWW-based PMC, so that the subscriber may directly send messages.
The PC 44 portion of the PMC application 44a may run under any suitable PC operating system, including those that present applications in windows. In accordance with an aspect of this invention the subscriber is able to rely on appointments and reminders being sent to his or her mobile station 10 in a timely manner. The mobile station 10 does not need to be connected by cable to the PC 44. Instead, the reminders can sent automatically from the network-connected PC 42, through the network 40 and PMC/WWW server 42, to the SMSC 36. The SMSC 36 then formats a suitable SMS message, either in accordance with the SMS signalling protocol of the applicable air interface standard or a presently preferred DESC format (described below), and causes the SMS message to be transmitted to the mobile station 10 through the MSC 34 and BS 30. Appointment, message and timely reminder texts can thus be sent from the desktop PC 44 to the subscriber's mobile station display 20.
For those times when the subscriber does not have access to the mobile station 10, and wishes to view and possibly respond to new messages, access is made to the PMC/WWW server 42. This access can be made through the network 40 from the PC 44 or a LAN-connected PC. The subscriber has immediate access, from anywhere in the world, to the PMC application with the WWW browser-equipped PC 44, personal digital assistant (PDA) device, or any suitable data processor capable of accessing the network 40. By example, the subscriber simply accesses the PMC application running at the PMC/WWW server 42 as he or she would any internet site. After the correct identification is made, the subscriber has access to the subscriber's messages and other information maintained by the PMC application running at the PMC/WWW server 42.
By example, one or more new calendar appointments may be entered by the subscriber directly into a window on the PC 44, or previous appointments may be reviewed, deleted, or revised, and the appointment or appointments are transferred automatically from the subscriber's PC-based calendar application that is running on the PC 44 to the PMC/WWW Server 42. For example, this could be done in the morning before the subscriber leaves the home or the office to make, for example, sales calls. Prior to each scheduled appointment a reminder is sent to the subscriber's mobile phone display 20, via the SMSC 36, MSC 34 and BS 30. The appointment reminder is received by mobile station 10 as a SMS message (preferably a DESC-encoded SMS message as described below), and is stored in the memory 24 for review by the subscriber, using the normal SMS message capabilities of the mobile station 10.
The Personal Messaging Calendar application also enables immediate SMS messaging from the PC 44 to the mobile station 10. An acknowledgment of receipt of the SMS messages by the mobile station 10 is also supported. A call-back number and reply charge-acceptance may also be selected on a per message basis.
In a presently preferred embodiment of this invention a Messaging Window of the Personal Messaging Calendar application running at the PC 44 accepts the appointment entries and messages into a graphical representation of the mobile station's display 20. That is, the subscriber may be presented with a similar user interface whether accessing the PMC application from the PC 44 or the mobile station 10. Basic editing functions may be performed within the display area. This allows the subscriber to enter the text as the subscriber wishes the text to be later displayed at the receiving mobile station 10.
Also in a presently preferred embodiment, the calendar entries can be selected to repeat at convenient intervals, and the subscriber is made aware of any scheduling conflicts entered into the calendar. A Message Validity time-out is configurable for those messages that are time critical, or that will become outdated at a certain time. The message reply destination is also configurable, with the default destination being the subscriber's cellular phone number. A warning is displayed if a message is sent when the SMSC 36 is not functioning. A confirmation is displayed when some number of re-try attempts finally achieve successful delivery.
Further in accordance with this invention any SMS Messages sent to the subscriber's mobile station 10 from other mobile subscribers may be copied to the PMC/WWW server 42 by the SMSC 36. This allows the PMC subscriber to view received SMS messages while not having cellular network access, after accessing the PMC/WWW server 42 through the network 40. The subscriber may add, edit, delete or send any message while in the PMC application running on the PMC/WWW server 42. Messages that have successfully reached the mobile station 10 are flagged so that only unread messages may be conveniently selected. Messages already read are moved from an `unread` or new message folder to an `old` message folder.
The subscriber may also originate messages from the Personal Message Center application. The messages may be sent to individuals or to groups. In a presently preferred embodiment of this invention the PMC application supports a list of possible messages, stored in folders, that may be selected to facilitate message origination. The subscriber may also create and store a list of phone numbers by parsing stored call-back numbers. Group mailing lists may be formed from the list of phone numbers in the PMC, which can be automatically updated by the PMC.
One important function of the Personal Message Center application is the management of the timed release of outgoing reminders and messages. The subscriber may add, edit, or delete messages while connected to the PMC application. All messages are preferably encrypted in order to pass securely through the network 40, such as the internet, to the Personal Message Center application running on the PMC/WWW server 42, and from the PMC/WWW server 42 to the SMSC 36 via the network 40 (as in the embodiment of FIG. 3).
Having thus described the invention in the context of the PMC application, a description will now be given of a presently preferred message format that is designed for, but is not limited to, exchanging information using SMS messaging protocols.
By way of introduction, it is noted that it may not be sufficient to simply transmit the message as normal text. Instead, the message needs to be encoded so that different parts of the message can be separated from each other and more readily interpreted. The message format described in detail below, referred to as the Data Exchange, Storage, and Command (DESC) format, fulfills this need.
It is also noted that although the various examples are shown below as occupying several lines of text, in practice a data set consists of one continuous stream of characters without line feeds.
Data Set
The data set holds all the information which is needed by an application. This includes the data set's identification, additional information for the application, and the actual data items.
The data set can be thought of as one unit which can be stored in a memory, exchanged among different applications, or sent from or received by the mobile station 10 via the air interface. A data set can have the appearance of a string, a SMS message, or any other structure that can accommodate ASCII characters. As used herein, ASCII characters refer to the standard character set of the applicable air interface standard (e.g., GSM or IS-136).
In principle, a data set can be of arbitrary length. In practice, however, the actual length is constrained by the data set's appearance. It may happen that the length of the information exceeds the length of a data set. In this case the information must be broken down into two or more data sets. The DESC format provides a mechanism to handle these situations, as will be described below.
The first two characters of a data set are two forward slashes //. These two slashes indicate that the remainder of the information is DESC-format encoded. The end of a data set is not specified, as it varies depending on the data set's appearance. For example, the end of a data set implemented in the C programming language is indicated by a `\0` (zero terminated string). The generic DESC format of a data set is: // <remainder of the information>.
Entry (General)
The <remainder of the information> consists of fields or entries. An entry holds all relevant information for one data item. A data set is made up of at least one entry (=application entry), and more (=data entries) can follow if required. Entries are separated from one other with a comma (,) delimiter. A given entry has three parts: the entry identifier, the entry options, and the entry value. The identifier, options and value parts are separated from each other with a colon (:) delimiter. The order of the entry parts is fixed as: identifier, options, value.
Application Entry
The application entry contains important information for the application which must process the information that follows after the application entry. There is always one, and only one, application entry in the data set. It is always the first entry. The three parts of an application entry are referred to as the application identifier, the application option, and the application value. A given application entry must have one application identifier, can have none, one, or several application options, and can have one application value.
The generic DESC format of an application entry is as follows:
<appl identifier>[:<appl option>[: . . . ]][:<appl value>]
All application options and application values are predefined to insure that any application that uses the DESC format can interpret the application entry. Also, an exemplary list of application identifiers is provided below.
An application identifier is the first part of an application entry. It names the application to which the data set is being sent. However, other applications may be able to interpret the data set if the data set contains common data identifiers. The application options give additional information to the destination application about the remainder of the DESC encoded information. An application entry may include none, one or several application options. An application value describes the type of the encoded information. The application value is not mandatory, and can be eliminated. However, if used only predefined application values are legal.
Data Entry
A data entry holds the actual data that the destination application is to work with. There can be none, one, or several data entries in a data set, and the data entries always follow after the application entry. The three parts of a data entry are referred to as the data identifier, the data option, and the data value. A given data entry must have one data identifier, can have no data option or can have several data options (if there is a data value), and can have one data value.
The generic DESC format of a data entry is as follows:
<data identifier>[[:<data option>[: . . . ]]:<data value>]
The data identifier is the first part of a data entry. It is a description for the value of the corresponding data entry. Data options are defined so as to give additional information about the data value. In practice, data options may be infrequently used, and are therefore application specific. Every application may define its own data options. A data entry may include none, one or several data options. The data value is the actual data which is referred to by the data identifier within the same data entry.
Basically, there is no restriction on what a data value may contain so long as it conforms to the specification given for a data set. A data value can consist of any sequence of letters, digits, blank spaces and punctuation marks. Commas (,) and colons (:) are handled differently.
Identifiers
An identifier consists of one letter or a sequence of letters and underscores. No blanks or white spaces are allowed. At least the first character of an identifier must be a letter. Identifiers are not case sensitive. There is no limitation in length for identifiers, but for practical purposes they are kept as short as possible.
The generic DESC format of an identifier is as follows:
<letter>[[<letter>|<underscore>] . . . ]
Where:
<letter>=<a . . . z|<A . . . Z>
<underscore>=--
Options
An option is split into several parts: the option identifier, the option argument, and the option value. The option identifier, option argument and option value build one sequence of characters. No blanks or white spaces are allowed.
The generic DESC format of an option is as follows:
<opt identifier>[[[[<opt value>]<opt argument>] . . . ]
<opt value>]
The option value is defined as zero (0) or any positive integer.
Arguments
The following characters may be used for arguments:
= < > - / .
The following character combinations may also be used for arguments:
<= >= <>
Other characters or combinations are not allowed.
Special Characters
Special attention is paid to two special characters: the comma (,) and the colon (:), as these characters are used as delimiters within the DESC format. If required as part of a data value, these characters are represented by repeating the character (for example, a comma is represented as ,,.
Multi-Language Support
Preliminary, predefined DESC identifiers and possible options are intended for applications, such as the PMC application described above, which use them for value references. For that reason, application and data identifiers are defined only in English.
Application Identifier
A list of presently preferred application identifiers is as follows.
Application Identifiers:
APP (Appointments)
TODO
ALERT
BC (Business Card)
HOURS
INFO
SALES
SPORT
STOCK
TIME (For combined time/date information)
WWW
Confirmation
This option requests the receiver of the message to confirm the reception of the encoded information. The form of the confirmation is a function of the application.
Identification
With this option, the data set can be given a unique identification.
ID<y>
where y can be 0 or any positive integer
Parts
With this option, the present data set can be marked as the mth part out of n parts in total. The values of m and n can be any positive integer. It is the application's responsibility to split and concatenate the parts of the data set in a correct manner. This option is used when it is impossible to pack the information to be sent within one data set. The above-described ID option can be used in connection with the PART option.
PART<m>/<n>
The PART option is especially useful when a PMC message or reminder exceeds the maximum length allocated for a SMS message in the Cellular system illustrated in FIGS. 2 and 3.
Version
This option indicates the version number of the application (e.g., PMC Ver. 1.0 or PMC Ver. 1.1) which has created the present data set. The variable x can be 0 or any positive integer.
VERS<x>[.<x>]
Application Value
The application value (value of the first entry of a data set) is reserved for application specific information. By not supplying any application value indicates the "standard information" of the application that is identified by the application identifier.
Error
The ERROR application value can be used by any application to indicate a fault in message processing.
Because of its intended universal application, the DESC specification does not define the contents of the data set for an error message. However, one of at least two generic formats can be followed.
1. If the erroneous data set is not clearly identified by an ID application option, then the full received message can be sent back to the sender with the addition of an ERROR application value and a corresponding data entry (data identifier=ERROR and data value=short error description). By example:
//
<application identifier>:ERROR
,ERROR:<short error description>
,<entries of received message>
2. If the received data set is identified by an ID application option, then the received application entry with the ERROR application value, a corresponding data entry (data identifier=ERROR and data value=short error description) and the erroneous data entry can be sent back to the sender of the erroneous message. By example:
//
<application identifier>:ID<y>:ERROR
,ERROR:<short error description>
,<erroneous data entry>
Command
A message with a COMMAND application value is constructed freely according to a conventional, generic format and an application's need. A command is usually sent to a specific application, such as the PMC application. However, several applications may use same command entry.
//
<application identifier>:COMMAND
,<command identifier>[[:<command options>]:<command value>]
[, . . . ]
By using the above-described ID application option, a command can be applied specifically to a certain message or data set without specifying additional command options or command values. For example:
//
<application identifier>:ID<y>:COMMAND
,<command identifier>
[, . . . ]
Reply
The REPLY application value can be used to identify the data set as an answer or a reply to a request or a command. The format is as follows:
//
<application identifier>:REPLY
,<data entry>
[, . . . ]
Query
The QUERY application value can be used if an application is to retrieve certain information from another application. Search criterion are given by specifying one or more data entries. If there is more than one data entry, they are ANDed for the search.
//
<application identifier>:QUERY
,<data entry>
[, . . . ]
Data Identifier
To ensure that applications can read information generated by other applications, a number of commonly used data identifiers and values are predefined by DESC as follows.
______________________________________                                    
TITLE:<a title>    (a header or summary)                                  
MSG:<a message>    (a text message)                                       
DATE:ddmm[yy]yy    (also used as starting date)                           
TIME:hhmm[ss]      (also used as starting time)                           
EDATE:ddmm[yy]yy   (end date)                                             
ETIME:hhmm[ss]     (end time)                                             
ADATE:ddmm[yy]yy   (Alert/Alarm date)                                     
ATIME:hhmm[ss]     (Alert/Alarm time)                                     
NAME:<name>                                                               
ADDRESS:<address>                                                         
TEL:<tel number>                                                          
EMAIL:<user@host>                                                         
FAX:<fax number>                                                          
ERROR:<error description>                                                 
______________________________________                                    
A number of the foregoing Data Identifiers are used by the PMC application software, including MSG, DATE, TIME, ETIME, and ADATE.
The above described DESC format thus specifies a way to encode information. Encoded information can be sent as short messages (e.g., SMS messages) to or from the mobile station 10. Any information that is encoded in DESC format can be stored in a memory or processed as any other character string, since it consists only of ASCII characters.
This following description demonstrates the flexibility of the DESC format, and illustrates various exemplary applications of DESC encoded information.
When provided in the mobile station 10, or other wireless communication device, a DESC Message Parsing option is selected from a displayed feature list. When selected, the mobile station 10 is able to recognize, then parse, DESC messages and display the result on the display 20.
To be able to parse and to present DESC encoded information, the mobile station's software must have a priori knowledge of the structure of the DESC message format. The mobile station 10 is not required to process the received data.
If an application or data identifier is not known to the mobile stations's software (for example, is not stored in a list of supported applications), then the application identifier or data identifier and the associated data value is shown "as is". However, if an application or data identifier is known to the software, it being assumed that the software maintains a pre-programmed list, which can be extended by sending another DESC message, then the application identifier or data identifier and its associated data value are translated and displayed in a more convenient, application specific format.
The procedure that is applied to displaying the DESC message need not differ from the procedure used for conventional SMS message handling. The application specific information that is displayed includes the application identifier and application value. The data specific information that is displayed consists of the data identifier and data value.
By example, the following DESC received message:
//
APP;ID982
,ERROR:<description>
,TITLE:LUNCH
,MSG:With Jim
,DATE:251098
,TIME:1230
,EDATE:251098
,ETIME:1345
may be displayed in a first display format as follows, when parsing is performed by the mobile station 10 (assuming that all identifiers are unknown, and DESC Message Parsing is selected from a displayed feature list):
NEW:
25-Oct-98
11:20:03
APP:
of type
ERROR<description>
TITLE:
Lunch
MSG:
With Jim
DATE:
251098
TIME:
1230
EDATE:
251098
ETIME:
1345
Sender:
+2125551212
However, the same DESC message may be shown as follows when parsed and suitably translated, where translation presupposes that both DESC Message Parsing and a PMC-related Calendar Translator Application are selected from the displayed feature list:
NEW:
Oct-25-98
11:20:03 A.M.
APPOINTMENT:
of type
ERROR<description>
TITLE:
Lunch
MESSAGE:
With Jim
DATE:
Oct. 25, 1998
TIME:
12:30 P.M.
END TIME:
1:45 P.M.
Sender:
+2125551212
Note that the above example of the Calendar Translator application has translated the abbreviated application and data identifiers into full words (English in this case, although any language (user selected) may be supported). Also, dates and times have been formatted in a local manner. Also, the end date information is optionally deleted, as the end date is equal to the start date. As such, the message is displayed in a second display format that differs significantly from the first display format.
Each application that may be parsed with the DESC Message Parsing feature have their own associated translation and executable features that may be selected from the user interface feature list.
Further in accordance with this invention the translator and execution features may be loaded into the mobile station 10, using the DESC format via SMS.
Referring now to FIG. 4 which illustrates a method in accordance with this invention, at Block A the mobile station 10 receives a SMS message. At Block B the mobile station 10 determines if the SMS message is in a first transfer format or a second transfer format. That is, it is determined if the SMS message is in a non-DESC format or the DESC format (as described above). If not in the DESC format, control passes to Block C to perform conventional SMS processing. If the received SMS message is in the DESC format control instead passes to Block D where the controller 18, operating under the control of DESC-related firmware or software, parses the DESC encoded SMS message. At Block E a determination is made if the Application Identifier is a known (to the mobile station) application identifier. As was described above, the application identifier is the first part of an application entry, and it names the application to which the data set is being sent. If the Application Identifier is known, control passes to Block F where the associated application (e.g., APP or appointments) is initiated (see the example presented above relating to the Lunch message). If the Application Identifier is not known (to the mobile station 10), control passes instead to Block G where the associated text message is presented without the application-specific formatting.
A subscriber having the mobile station 10 is enabled to access a desired application using a displayed menu. After selecting the desired application the subscriber may manipulate soft keys and the keypad 22 so as to enter information in response to prompts (assuming that the mobile station does not include a touch screen or some other suitable user interface). By example, to enter an appointment into the PMC application, the following display may be presented.
TITLE A title for the appointment.
TEXT A description for the appointment (e.g., Lunch with Jim, the location of the restaurant, etc.).
START INFO. The subscriber enters the starting date and time for the appointment.
END INFO. The subscriber enters the ending date and time for the appointment.
ALERT INFO. The subscriber enters an alert date and time for the appointment (e.g., one hour prior to the Start time).
After the last information screen is filled in (i.e., Alert Info.), a SAVE soft key can be depressed. Depressing the SAVE soft key initiates sending the entered information to the PMC/WWW server 42. The appointment information is sent to the PMC/WWW server 42 using a DESC-encoded SMS message, via the RF link, BS 30, MSC 34, SMSC 36, and one of the link 42a or the network 40. At a time corresponding to the Alert time, the PMC/WWW server 42 initiates the sending of a DESC-encoded SMS message to the mobile station 10, via a path that is the reverse of that used to send the appointment information to the PMC/WWW server 42.
It is also within the scope of this invention to send a message receipt confirmation message back to the mobile station 10 from the PMC/WWW server 42. In response to the receipt of the confirmation message, the mobile station 10 displays a suitable message (e.g., `Appointment Saved`) along with the Appointment Title. In this case the subscriber is assured that the appointment has been saved in the master appointment database 43a maintained by the PMC/WWW server 42.
At some subsequent time, identified by the Alert information, a SMS message is sent to the mobile station 10. One suitable displayed message format is to display the text "Reminder", along with the text "At" followed by the Time of the appointment, if the time was saved with the appointment.
The subscriber may also interact with the display 20 and keypad 22 to view existing appointments for a particular date. In this case the mobile station 10 sends a SMS message to the PMC/WWW server 42, after prompting the subscriber to enter the date of interest. After receiving the saved appointment information from the PMC/WWW server 42 and saving the information in the memory 24, a message "Appointments Received" can be displayed. Thereafter the subscriber can scroll through the appointments that were previously saved for the date of interest, which may be displayed by Title.
Similar or identical functionality is available from the PC 44, thereby providing the subscriber with multiple ways to access the information, while providing a unified and self-consistent user interface.
Although described in the context of entering Appointment events, the subscriber is also enabled to instead enter a "To Do" reminder or event. By example, to enter a "To Do" into the PMC application, the following display may be presented.
TITLE A title for the "To Do" entry.
TEXT A description of the "To Do" (e.g., `final sales report`).
PRIORITY A subscriber-assigned priority for this "To Do" entry (1, 2, 3).
DEADLINE A deadline date for this "To Do" entry.
As with the Appointment entry described above, after the last information screen is filled in (i.e., Deadline), a SAVE soft key can be depressed. Depressing the SAVE soft key initiates sending the entered information to the PMC/WWW server 42. The "To Do" information is sent to the PMC/WWW server 42 using a DESC-encoded SMS message, via the RF link, BS 30, MSC 34, SMSC 36, and one of the link 42a or the network 40.
The subscriber may also interact with the display 20 and keypad 22 to view, delete, and edit existing "To Do" entries. In this case the subscriber may select to view all "To Do" entries in the list, or to view only those "To Do" entries having a specified priority class or level. In this latter case the mobile station 10 sends a SMS message to the PMC/WWW server 42, after prompting the subscriber to enter the desired priority class. After receiving the previously saved "To Do" information from the PMC/WWW server 42 and storing the information in the memory 24, a message "To Do List Received" can be displayed. Thereafter the subscriber can scroll through the "To Do" entries that were previously saved for the desired priority class.
The subscriber can also interact with the display 20 and keypad 22 to delete and revise previously saved Appointment and "To Do" entries. Also, and as was described above, the subscriber can also gain access to the subscriber's database 43a entries in the PMC/WWW server 42 via the PMC software installed in the PC 44. In this manner various Appointment and "To Do" entries can be entered, saved, reviewed and modified from the PC 44. In both cases (e.g., mobile station access or PC access), the presently preferred DESC format is used (with any suitable modifications that may be required in order to pass through the network 40). Also in both cases, the subscriber is enabled to store information relating to some event, typically a future event, in the database 43a that is coupled to the messaging function or SMSC 36.
Although described in the context of the PMC application, it should be realized that this particular application is exemplary, and should not be read as a limitation on the practice of this invention. That is, other valuable applications can also be implemented in accordance with the teachings of this invention. By example, other potential applications of this invention include, but are not limited, using SMS-based messaging between groups of mobile stations and PCs for queued and scheduled email; for meeting, appointment and absence management; for project hours reporting; for sales and inventory updating; for personalized information services; and for home security applications.
Further by example, a subscriber can be notified of the receipt of email by storing the notification and/or the email header information into the database 43a. This can be done from a data processor that functions as an email server 48. In this example the Alert time could be set to zero. That is, subscriber-related information and events can be stored in the database 43a by other than the subscriber or the SMSC 36, in this case by the email server 48.
In a presently preferred embodiment of this invention, and referring again to FIG. 1, a non-volatile portion 24b of the memory 24 is allocated for local storage (LS). The local storage 24b may be allocated either statically or dynamically. The local storage 24b can be used to store the user's events to be viewed immediately or when out of a cellular coverage area. The local storage 24b can also be used to temporarily store added or modified user events when out of the cellular coverage area. After the mobile station 10 is once more in a cellular coverage area the stored events can be transmitted to the PMC/WWW Server 42 using the protocols described above. The user can also employ the local storage 24b to temporarily store events should the user decide to postpone a reply action for a received alert. The local storage 24b also provides a mechanism to generate locally triggered alerts. For example, the user stores an alert in the local storage 24b, which is then checked by local PMC application software 24a using an internal real-time clock (RTC) 21. An alert is then triggered locally when the current time matches the time stored with the alert in the local storage 24b. Both user-generated information and information received from the BMI 32 can be stored in the local storage 24b.
It is also within the scope of this invention to provide the user interface of the PC/PMC 44a with a special screen saver or similar software. This screen saver may function as any conventional password-protected screen saver, but in addition displays a floating or moving window. Using the window anyone visiting the user's PC site (such as an associate in the user's office) can enter a SMS message. After completing the message a predetermined keystroke or mouse click causes the entered SMS message to be transferred automatically to the user's mobile station 10 via the PMC/WWW Server 42 and SMSC 36.
Thus, although the invention has been described in the context of preferred embodiments, it should be realized that a number of modifications to these teachings may occur to one skilled in the art. Thus, while the invention has been particularly shown and described with respect to preferred embodiments thereof, it will be understood by those skilled in the art that changes in form and details may be made therein without departing from the scope and spirit of the invention.

Claims (9)

What is claimed is:
1. A method for operating a wireless mobile station of a type that is capable of bidirectional communication with a Base Station, Mobile Switching Center, Interworking Function (BMI) having a Short Message Service (SMS) center, comprising the steps of:
receiving a SMS message from the BMI;
determining if the SMS message has a first transfer format or a second transfer format;
if the SMS message is determined to have the first transfer format, processing the SMS message in a conventional manner;
if the SMS message is determined to have the second transfer format, parsing the SMS message to locate an Application Identifier entry;
determining from the Application Identifier entry if the mobile station supports the identified application;
if not, displaying any data entry of the SMS message with a first display format; else,
if the mobile station does support the identified application, starting the application and displaying any data entry with a second display format that is specified by the application.
2. A method as set forth in claim 1, wherein the second transfer format is a Data Exchange, Storage, and Command (DESC) format.
3. A method as set forth in claim 1, wherein the SMS message is encoded to identify an event that was previously stored in a database, the SMS message being sent to the mobile station at a time specified in the database.
4. A method as set forth in claim 3, wherein information specifying the event was previously stored in the database in response to a SMS message that was originated by the mobile station.
5. A method as set forth in claim 3, wherein information specifying the event was previously stored in the database in response to a message that was originated by a data processor coupled to the database through a communications network.
6. A method as set forth in claim 3, wherein information specifying the event was previously revised after storage in the database in response to a SMS message that was originated by the mobile station.
7. A method as set forth in claim 3, wherein information specifying the event was previously revised after storage in the database in response to a message that was originated by a data processor coupled to the database through a communications internet.
8. A method as set forth in claim 1, wherein the SMS message is encoded to identify a prioritized event that was previously stored in a database, the SMS message being sent to the mobile station in response to a query from the mobile station to display all stored events having a specified priority level.
9. A method as set forth in claim 1, wherein the SMS message is encoded to identify an event that was previously stored in a database, the SMS message being sent in response to a query from the mobile station to display all stored events having a specified date.
US09/347,756 1997-01-31 1999-07-06 Real-time SMS application messaging using an SMSC-linked server Expired - Lifetime US6078820A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/347,756 US6078820A (en) 1997-01-31 1999-07-06 Real-time SMS application messaging using an SMSC-linked server

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US3677097P 1997-01-31 1997-01-31
US08/811,550 US6125281A (en) 1997-01-31 1997-03-04 Real-time SMS application messaging using an SMSC-linked server
US09/347,756 US6078820A (en) 1997-01-31 1999-07-06 Real-time SMS application messaging using an SMSC-linked server

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US08/811,550 Division US6125281A (en) 1997-01-31 1997-03-04 Real-time SMS application messaging using an SMSC-linked server

Publications (1)

Publication Number Publication Date
US6078820A true US6078820A (en) 2000-06-20

Family

ID=26713483

Family Applications (2)

Application Number Title Priority Date Filing Date
US08/811,550 Expired - Lifetime US6125281A (en) 1997-01-31 1997-03-04 Real-time SMS application messaging using an SMSC-linked server
US09/347,756 Expired - Lifetime US6078820A (en) 1997-01-31 1999-07-06 Real-time SMS application messaging using an SMSC-linked server

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US08/811,550 Expired - Lifetime US6125281A (en) 1997-01-31 1997-03-04 Real-time SMS application messaging using an SMSC-linked server

Country Status (5)

Country Link
US (2) US6125281A (en)
EP (1) EP0956719A2 (en)
JP (1) JP2001509981A (en)
AU (1) AU6214998A (en)
WO (1) WO1998034422A2 (en)

Cited By (86)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6263212B1 (en) * 1998-02-17 2001-07-17 Alcatel Usa Sourcing, L.P. Short message service center
US6292657B1 (en) * 1998-07-13 2001-09-18 Openwave Systems Inc. Method and architecture for managing a fleet of mobile stations over wireless data networks
US6327479B1 (en) * 1997-09-22 2001-12-04 Nokia Networks Oy Procedure and system for the transmission of a short message in a telecommunication network
US20020003882A1 (en) * 2000-03-21 2002-01-10 Barry Jones Method of, and means for, delivering information services over the air
US6341228B1 (en) * 1998-05-07 2002-01-22 Alcatel Method of parameterizing the display on mobile radio communications equipment co-operating with a subscriber identity module
US20020013711A1 (en) * 2000-04-14 2002-01-31 Arun Ahuja Method and system for notifying customers of transaction opportunities
US20020046299A1 (en) * 2000-02-09 2002-04-18 Internet2Anywhere, Ltd. Method and system for location independent and platform independent network signaling and action initiating
WO2002032171A1 (en) * 2000-10-09 2002-04-18 Telstra New Wave Pty Ltd Message processing
US6400811B1 (en) 1997-07-30 2002-06-04 Internet2Anywhere Ltd. System and method for off-line notifying a network user
US20020081997A1 (en) * 2000-11-07 2002-06-27 Masaaki Morishima Mobile terminal, display switching method of mobile terminal, and recording medium for recording display switching program
US20020087656A1 (en) * 2000-10-25 2002-07-04 Michael Gargiulo Downloadable multimedia content and method for accounting
KR20020060382A (en) * 2001-01-10 2002-07-18 이중한 Method and system of dual SMS number service
US20020098855A1 (en) * 1996-09-27 2002-07-25 Peter Hartmaier Mobility extended telephone application programming interface and method of use
US20020115424A1 (en) * 2001-02-20 2002-08-22 Bagoren Sevket Ilhan Replenishment of pre-paid wireless telephone accounts using short message service (SMS)
US20020123359A1 (en) * 2000-12-01 2002-09-05 Multiscience System Pte Limited Network for information transfer for mobile stations
US20020156936A1 (en) * 2001-02-16 2002-10-24 Microsoft Corporation System and method for providing componentized transports and forms
US6560456B1 (en) 1999-05-24 2003-05-06 Openwave Systems, Inc. System and method for providing subscriber-initiated information over the short message service (SMS) or a microbrowser
US20030114140A1 (en) * 2000-05-30 2003-06-19 Jukka-Pekka Iivonen Billing for replies in a communication system
US20030114174A1 (en) * 2001-12-19 2003-06-19 Brian Walsh Mobile telephone short text messaging with message thread identification
WO2003053022A1 (en) * 2001-12-14 2003-06-26 Spl Innotech Pte Ltd. Messaging system
US6587684B1 (en) * 1998-07-28 2003-07-01 Bell Atlantic Nynex Mobile Digital wireless telephone system for downloading software to a digital telephone using wireless data link protocol
US6633318B1 (en) * 1997-12-26 2003-10-14 Samsung Electronics Co., Ltd. Screen saver having message management function and method therefor
US6639941B1 (en) * 1998-12-04 2003-10-28 Nec Corporation Radio-signal transceiver
US6668059B1 (en) 2000-04-16 2003-12-23 Internet2Anywhere, Ltd. Telephone tuning and signaling system
US6684087B1 (en) * 1999-05-07 2004-01-27 Openwave Systems Inc. Method and apparatus for displaying images on mobile devices
US20040029598A1 (en) * 2000-10-20 2004-02-12 Karl Guggisberg Method for transmitting short messages over the internet
US20040142708A1 (en) * 2003-01-17 2004-07-22 Hitachi, Ltd. Communication apparatus and communication system
US6771981B1 (en) 2000-08-02 2004-08-03 Nokia Mobile Phones Ltd. Electronic device cover with embedded radio frequency (RF) transponder and methods of using same
US20040196866A1 (en) * 2002-09-16 2004-10-07 Samsung Electronics Co., Ltd. Method for transmitting and recording schedule using short message service
US20040203606A1 (en) * 2002-03-13 2004-10-14 Novatel Wireless, Inc. Complete message delivery to multi-mode communication device
US6816083B2 (en) 2002-02-04 2004-11-09 Nokia Corporation Electronic device with cover including a radio frequency indentification module
US20040266408A1 (en) * 2003-06-25 2004-12-30 Oracle International Corporation Mobile messaging concierge
US20050002510A1 (en) * 1999-11-12 2005-01-06 Metro One Telecommunications, Inc. Technique for providing personalized information and communications services
US20050015443A1 (en) * 2000-10-10 2005-01-20 Alex Levine Personal message delivery system
US20050017068A1 (en) * 1995-02-15 2005-01-27 Zalewski Thomas W. System and method of making payments using an electronic device cover with embedded transponder
WO2005015423A1 (en) * 2003-07-11 2005-02-17 Vazu, Inc. Method and system for transferring contact information to an sms-enabled wireless device
US20050070314A1 (en) * 2001-10-26 2005-03-31 Jeffrey Wilson Telecommunications services apparatus
US20050176449A1 (en) * 2004-02-05 2005-08-11 Yahoo! Inc. Method and system for simplified access to alerts with a mobile device
US20050188320A1 (en) * 2004-02-24 2005-08-25 Bocking Andrew D. Method and system for managing unread electronic messages
US20050222754A1 (en) * 2004-03-30 2005-10-06 Naftali Meisler SMS vehicle information system
US20060059232A1 (en) * 2002-06-26 2006-03-16 Masato Yoshikawa Message transmission/reception system and method
US20060199597A1 (en) * 2005-03-02 2006-09-07 Cisco Technology, Inc. System and method for providing a proxy in a short message service (SMS) environment
WO2006126140A2 (en) * 2005-05-27 2006-11-30 Koninklijke Philips Electronics N.V. Method and apparatus for processing data
US7149537B1 (en) * 2002-02-12 2006-12-12 Cellco Partnership Method and system for generating a user-accessible internet-based mobile messaging log
US20060293937A1 (en) * 2005-06-24 2006-12-28 Mark Sohm System and method of wireless carpool scheduling
US20070053518A1 (en) * 2000-01-13 2007-03-08 Peter Tompkins Method and system for conducting financial and non-financial transactions using a wireless device
US20070174448A1 (en) * 2000-04-14 2007-07-26 Arun Ahuja Method and system for notifying customers of transaction opportunities
US20070265022A1 (en) * 2006-05-11 2007-11-15 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US20070265023A1 (en) * 2006-05-11 2007-11-15 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US20070270129A1 (en) * 2006-05-19 2007-11-22 Hui Luo Method and system for using a mobile terminal as a location-based reminder
WO2008016722A2 (en) * 2006-07-31 2008-02-07 Sony Ericsson Mobile Communications Ab A network interface for a wireless communication device
WO2008037356A1 (en) 2006-09-27 2008-04-03 T-Mobile International Ag Method for service identification for convergent messaging systems
US20080163111A1 (en) * 2006-12-29 2008-07-03 Research In Motion Limited Streamlined entry of appointment record
US20080255919A1 (en) * 2007-04-10 2008-10-16 Gorder Douglas P System and method for schedule notification
US20090112926A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Utilizing Presence Data Associated with a Resource
US20090112996A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Determining Presence Status of End User Associated with Multiple Access Terminals
US20090112997A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Utilizing Presence Data Associated with Web Item
US20090176506A1 (en) * 2003-01-31 2009-07-09 Qualcomm Incorporated Location based service (lbs) system, method and apparatus for triggering of mobile station lbs applications
WO2009118064A1 (en) * 2008-03-28 2009-10-01 Carryquote Ag Data communication of fixed size data packages
US20100041368A1 (en) * 2008-08-12 2010-02-18 Pradeep Kumar Methods, systems and computer readable media for electronically delivering a prepaid card to a mobile device
US7680505B2 (en) 2000-10-27 2010-03-16 Cellemetry, Llc Telemetry gateway
US7680471B2 (en) 2006-05-17 2010-03-16 Numerex Corp. System and method for prolonging wireless data product's life
US20100174598A1 (en) * 2008-12-31 2010-07-08 Mohammad Khan Methods, systems and computer readable media for redeeming and delivering electronic loyalty reward certificates using a mobile device
US20100197326A1 (en) * 2006-10-19 2010-08-05 Duc Anh Ngo interactive system and process
US7783508B2 (en) 1999-09-20 2010-08-24 Numerex Corp. Method and system for refining vending operations based on wireless data
WO2010097590A3 (en) * 2009-02-26 2010-10-21 Sepura Plc Transmission of encrypted short data messages in communications systems
US20100273521A1 (en) * 2003-03-06 2010-10-28 Gemplus Method for managing the triggering of an application in a service terminal, particularly in a telecommunication terminal
US20100273450A1 (en) * 2009-04-27 2010-10-28 Papineau Scott A Apparatus and method for activating computer applications with sms messaging
US7880599B2 (en) 2004-01-21 2011-02-01 Numerex Corp. Method and system for remotely monitoring the operations of a vehicle
US20110117895A1 (en) * 2002-11-07 2011-05-19 Research In Motion Limited Pseudo-interactive input processing in wireless environments
US8055286B1 (en) 2008-08-27 2011-11-08 Sprint Spectrum L.P. Modification of en-route message to add destination port number selected based at least in part on message originator
US20120198012A1 (en) * 2002-11-18 2012-08-02 Aol Inc. Enhanced buddy list using mobile device identifiers
US8265605B2 (en) 2007-02-06 2012-09-11 Numerex Corp. Service escrowed transportable wireless event reporting system
ITMI20110394A1 (en) * 2011-03-14 2012-09-15 Leo Pillon SYSTEM AND METHOD FOR THE MANAGEMENT OF REMOTE DEVICE OPERATIONS.
US20120250593A1 (en) * 2011-03-31 2012-10-04 Majeti Venkata C Ubiquitous user control for information communicated among end user communication devices
US8336762B1 (en) 2008-11-17 2012-12-25 Greenwise Bankcard LLC Payment transaction processing
US8346677B1 (en) 2000-12-29 2013-01-01 Citicorp Development Center, Inc. Method and system for conducting commerce over a wireless communication network
US8403741B2 (en) 2011-03-10 2013-03-26 Riangelo Javier de Cuba SMS messaging system accommodating variable entries for lotteries
US8408992B2 (en) 2011-03-10 2013-04-02 Riangelo Javier de Cuba SMS payment system having chargeback to subscriber telephone account
US9070118B2 (en) 2003-09-05 2015-06-30 Facebook, Inc. Methods for capturing electronic messages based on capture rules relating to user actions regarding received electronic messages
US9191793B2 (en) 2007-10-19 2015-11-17 Duc Anh Ngo Interactive system and process
US9767452B2 (en) 2011-11-03 2017-09-19 Mastercard International Incorporated Methods, systems, and computer readable media for provisioning and utilizing an aggregated soft card on a mobile device
US10026076B2 (en) 2008-10-06 2018-07-17 Mastercard International Incorporated Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices
US10187334B2 (en) 2003-11-26 2019-01-22 Facebook, Inc. User-defined electronic message preferences
US10992817B2 (en) 2009-03-18 2021-04-27 Mastercard International Incorporated Methods, systems and computer readable media for selecting and delivering electronic value certificates using a mobile device
US11195163B2 (en) 2006-09-01 2021-12-07 Mastercard International Incorporated Methods, systems and computer readable media for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities

Families Citing this family (170)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6150955A (en) 1996-10-28 2000-11-21 Tracy Corporation Ii Apparatus and method for transmitting data via a digital control channel of a digital wireless network
US20060195595A1 (en) 2003-12-19 2006-08-31 Mendez Daniel J System and method for globally and securely accessing unified information in a computer network
US6708221B1 (en) 1996-12-13 2004-03-16 Visto Corporation System and method for globally and securely accessing unified information in a computer network
FI113823B (en) * 1997-03-13 2004-06-15 Nokia Corp Systems for processing service data in a telecommunications system
US5978770A (en) * 1997-04-24 1999-11-02 Visible Interactive Corporation Assigning and managing patron reservations for distributed services using wireless personal communication devices
DE19730159B4 (en) * 1997-07-14 2006-01-19 Telefonaktiebolaget Lm Ericsson (Publ) Communication method and system
SE509926C2 (en) * 1997-08-29 1999-03-22 Telia Ab Communication system including transmission of internet address by SMS
US6826407B1 (en) 1999-03-29 2004-11-30 Richard J. Helferich System and method for integrating audio and visual messaging
US6253061B1 (en) 1997-09-19 2001-06-26 Richard J. Helferich Systems and methods for delivering information to a transmitting and receiving device
US7003304B1 (en) 1997-09-19 2006-02-21 Thompson Investment Group, Llc Paging transceivers and methods for selectively retrieving messages
FI104604B (en) * 1997-09-19 2000-02-29 Nokia Networks Oy Updating Internet access point settings in the mobile system
US6636733B1 (en) 1997-09-19 2003-10-21 Thompson Trust Wireless messaging method
FI109733B (en) * 1997-11-05 2002-09-30 Nokia Corp Utilizing the content of the message
US6230004B1 (en) * 1997-12-01 2001-05-08 Telefonaktiebolaget Lm Ericsson Remote procedure calls using short message service
US20040107208A1 (en) * 1997-12-09 2004-06-03 Seet Siew Shon Method and apparatus for bookmarking telephone numbers for efficient access by wireless phone devices
US6983138B1 (en) 1997-12-12 2006-01-03 Richard J. Helferich User interface for message access
US6832084B1 (en) * 1998-01-07 2004-12-14 Microsoft Corporation Wireless database environment
EP0936827A1 (en) * 1998-02-17 1999-08-18 Koninklijke Philips Electronics N.V. Telephone system with a base station and at least one subscriber station, containing a callback device, and callback method
DE19808368B4 (en) * 1998-02-27 2004-12-09 Siemens Ag Method and arrangement for providing performance features via a communication network
US9374435B2 (en) 1998-05-29 2016-06-21 Blackberry Limited System and method for using trigger events and a redirector flag to redirect messages
US6438585B2 (en) 1998-05-29 2002-08-20 Research In Motion Limited System and method for redirecting message attachments between a host system and a mobile data communication device
US6779019B1 (en) 1998-05-29 2004-08-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6463463B1 (en) * 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing calendar event messages from a host system to a mobile data communication device
US6219694B1 (en) 1998-05-29 2001-04-17 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device having a shared electronic address
US8516055B2 (en) 1998-05-29 2013-08-20 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device in a wireless data network
US7209949B2 (en) 1998-05-29 2007-04-24 Research In Motion Limited System and method for synchronizing information between a host system and a mobile data communication device
DE19830333B4 (en) * 1998-07-07 2004-04-08 Siemens Ag Method for providing features for mobile subscribers over a communication network
KR100293996B1 (en) * 1998-08-06 2001-07-12 윤종용 Advanced transfering method of short message in digital portable telephone
JP2000092192A (en) * 1998-09-11 2000-03-31 Sharp Corp Portable communication terminal equipment
DE19856440C2 (en) 1998-12-08 2002-04-04 Bosch Gmbh Robert Transmission frame and radio unit with transmission frame
DE19861323B4 (en) 1998-12-08 2006-02-16 Robert Bosch Gmbh Method for transmitting short messages
US6594255B1 (en) * 1999-02-09 2003-07-15 Tadiran Telecom Business Systems Ltd. PBX with short messaging service on a telephone display
DE19925220A1 (en) * 1999-06-01 2000-12-14 Siemens Ag Method and arrangement for sending a message
IES20000432A2 (en) * 1999-06-01 2001-02-21 Markport Ltd Adaptation of WAP to SMS in PDC networks
US6463292B1 (en) * 1999-06-04 2002-10-08 Lucent Technologies Inc. System and method for redirecting data messages
KR100309526B1 (en) * 1999-06-24 2001-11-01 윤종용 Advanced short message service apparatus of digital portable terminal equipment and controling method thereof
US6549776B1 (en) * 1999-07-30 2003-04-15 Telefonaktiebolaget Lm Ericsson (Publ) System, method, and apparatus for pushing data in a direct digital call environment
US20010047394A1 (en) 1999-09-10 2001-11-29 Kloba David D. System, method, and computer program product for executing scripts on mobile devices
US8595308B1 (en) 1999-09-10 2013-11-26 Ianywhere Solutions, Inc. System, method, and computer program product for server side processing in a mobile device environment
WO2001018688A2 (en) 1999-09-10 2001-03-15 Avantgo, Inc. System, method, and computer program product for interactive interfacing with mobile devices
US6751463B1 (en) 1999-10-04 2004-06-15 Telecommunication Systems, Inc. Intelligent queue for information teleservice messages with superceding updates
US6795711B1 (en) * 1999-10-07 2004-09-21 Nokia Mobile Phones Ltd Multimedia message content adaptation
US20010014085A1 (en) * 1999-10-08 2001-08-16 Microsoft Corporation Originator authentication
US20010015977A1 (en) * 1999-10-08 2001-08-23 Stefan Johansson Selective reception
US6526274B1 (en) * 1999-10-25 2003-02-25 Comdial Corporation Method, system, and computer program product for extending the functionality of a personal information manager to telephone system interactions
US6625460B1 (en) * 1999-12-21 2003-09-23 Nokia Corporation Unified messaging protocol using SMS
US6728530B1 (en) * 1999-12-28 2004-04-27 Nokia Corporation Calendar-display apparatus, and associated method, for a mobile terminal
DE10009837A1 (en) * 2000-02-24 2001-09-06 Mannesmann Ag Coordination of working group information involves performing coordination with mobile terminal(s) over mobile radio telecommunications network under control of data processing device
US6714793B1 (en) 2000-03-06 2004-03-30 America Online, Inc. Method and system for instant messaging across cellular networks and a public data network
GB2360174B (en) * 2000-03-09 2004-01-07 Ericsson Telefon Ab L M Communications system
US7739334B1 (en) * 2000-03-17 2010-06-15 Visto Corporation System and method for automatically forwarding email and email events via a computer network to a server computer
AU4092201A (en) * 2000-03-21 2001-10-03 Magic4 Limited Method and system for delivering information services
WO2001072001A2 (en) * 2000-03-21 2001-09-27 Magic4 Limited Method of, and means for charging of delivering mobile or wireless information services
EP1275070B1 (en) * 2000-04-18 2007-01-03 British Airways PLC A method of operating a ticketing system
GB0009599D0 (en) * 2000-04-18 2000-06-07 British Airways Plc A method of operating a ticketing system
JP3642004B2 (en) 2000-05-22 2005-04-27 日本電気株式会社 Relay device, mobile radio communication system, failure notification method thereof, and recording medium recording failure notification program thereof
WO2001095558A1 (en) * 2000-06-05 2001-12-13 Matsushita Mobile Communication Development Corporation Of U.S.A. Protocol for short mail message encryption
EP1295492A1 (en) * 2000-06-19 2003-03-26 Mobilespear Ltd. System and method for object access through an access device
KR20000059233A (en) * 2000-07-24 2000-10-05 송왕섭 A method for managing wireless phone messages and a system thereof
KR100703420B1 (en) * 2000-08-22 2007-04-03 삼성전자주식회사 Method and system for short message transmitter/receiver chick in inter net in private radio net
US7225231B2 (en) * 2000-09-20 2007-05-29 Visto Corporation System and method for transmitting workspace elements across a network
US6804707B1 (en) 2000-10-20 2004-10-12 Eric Ronning Method and system for delivering wireless messages and information to personal computing devices
US20020055986A1 (en) * 2000-11-08 2002-05-09 Lavaflow, Llp Method of downloadinga screen saver to a cellular telephone
WO2002039779A1 (en) * 2000-11-08 2002-05-16 King, John, J. Method of displaying a picture file on a cellular telephone
US20020055992A1 (en) * 2000-11-08 2002-05-09 Lavaflow, Llp Method of providing a screen saver on a cellular telephone
KR100384279B1 (en) * 2000-11-15 2003-05-16 엘지전자 주식회사 Method for Replying Received Short Message in Mobile Communication Terminal
US6484033B2 (en) * 2000-12-04 2002-11-19 Motorola, Inc. Wireless communication system for location based schedule management and method therefor
GB2370190A (en) * 2000-12-13 2002-06-19 Matsushita Comm Ind Uk Ltd Third party call control
JP2002199080A (en) * 2000-12-22 2002-07-12 Toshiba Corp Mobile radio terminal
CA2640713C (en) 2000-12-22 2011-11-15 Research In Motion Limited Wireless router system and method
SE518751C2 (en) * 2001-01-03 2002-11-19 Microsoft Corp Method and system where an external server receives information on individual mobile terminals' radio transmission capacity
CA2368404C (en) 2001-01-18 2005-08-09 Research In Motion Limited Unified messaging system and method
KR100416342B1 (en) * 2001-02-06 2004-01-31 주식회사 케이티프리텔 A method for receiving data using SMS and wireless Internet and system thereof
AT411807B (en) * 2001-02-14 2004-05-25 Universal Comm Platform Ag METHOD AND DEVICE FOR FORWARDING SHORT MESSAGES FROM A MOBILE TERMINAL
ES2189628B1 (en) * 2001-02-27 2004-10-01 Airtel Movil, S.A. SYSTEM OF TRANSMISSION / RECEPTION OF SHORT MESSAGES (SMS) BETWEEN MOBILE TERMINALS AND REMOTE SERVERS.
US7145875B2 (en) * 2001-03-05 2006-12-05 Tekelec Methods and systems for preventing short message service (SMS) message flooding
US8054971B2 (en) * 2001-04-27 2011-11-08 Comverse Ltd Free-hand mobile messaging-method and device
EP1262931A1 (en) * 2001-06-01 2002-12-04 Siemens Aktiengesellschaft Improvements in text messaging
KR100442941B1 (en) * 2001-07-06 2004-08-04 엘지전자 주식회사 Broadcast message transmission circuit and transmitting Method thereof
US20030016639A1 (en) * 2001-07-19 2003-01-23 Ericsson Inc. Telecommunications system and method for delivery of short message service messages to a mobile terminal in data mode
US6954781B2 (en) * 2001-08-01 2005-10-11 International Business Machines Corporation Messaging system for directing a server to convert voice message into text and appending a converted text message to another converted text message
EP2247086B1 (en) * 2001-08-10 2017-08-02 Siemens Aktiengesellschaft Method, device and software program for expanding the information flow when transferring a message
US20030065715A1 (en) * 2001-08-20 2003-04-03 Burdick William R. System and method of a wireless thin-client, server-centric framework
US6658260B2 (en) 2001-09-05 2003-12-02 Telecommunication Systems, Inc. Inter-carrier short messaging service providing phone number only experience
US7050408B2 (en) * 2001-09-26 2006-05-23 Microsoft Corporation Communicating multi-part messages between cellular devices using a standardized interface
ES2190742A1 (en) * 2001-10-17 2003-08-01 Telefonica Moviles S A Distribution and management system for mobile telephony short messages and communication protocol for implementing said system
CA2410118C (en) 2001-10-26 2007-12-18 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US7793334B2 (en) 2001-11-16 2010-09-07 At&T Mobility Ii Llc System and method for password protecting a distribution list
US8660537B2 (en) * 2001-11-16 2014-02-25 At&T Mobility Ii Llc System for the storage and retrieval of messages
US7487262B2 (en) 2001-11-16 2009-02-03 At & T Mobility Ii, Llc Methods and systems for routing messages through a communications network based on message content
US7617328B2 (en) * 2001-11-16 2009-11-10 At&T Mobility Ii Llc System for translation and communication of messaging protocols into a common protocol
US20030096605A1 (en) * 2001-11-16 2003-05-22 Schlieben Karl J. System for handling proprietary files
US7549096B2 (en) 2001-11-16 2009-06-16 At&T Mobility Ii Llc Methods and systems for tracking and playing back errors in a communications network
US7317697B2 (en) 2001-11-16 2008-01-08 At&T Mobility Ii Llc System for handling file attachments
US7657253B2 (en) 2001-11-16 2010-02-02 At&T Mobility Ii Llc System and method for providing message notification
US7454195B2 (en) 2001-11-16 2008-11-18 At&T Mobility Ii, Llc System for the centralized storage of wireless customer information
US7319858B2 (en) * 2001-11-16 2008-01-15 Cingular Wireless Ii, Llc System and method for querying message information
US7401148B2 (en) 2001-11-16 2008-07-15 At&T Mobility Ii Llc System for customer access to messaging and configuration data
EP1454502B1 (en) * 2001-12-07 2014-11-12 BlackBerry Limited Advanced operations in a wireless device
WO2003049384A1 (en) * 2001-12-07 2003-06-12 Research In Motion Limited System and method of managing information distribution to mobile stations
ES2208038B1 (en) * 2001-12-10 2005-09-01 Airtel Movil, S.A. SHORT MESSAGE STORAGE SYSTEM (SMS).
EP1320273A1 (en) * 2001-12-12 2003-06-18 SCHLUMBERGER Systèmes System and method for loading data in a smart card through a telecommunication network.
GB2383494B (en) 2001-12-19 2006-01-25 Qualcomm A method of and apparatus for handling messages in a mobile communications environment
US7116994B2 (en) * 2001-12-21 2006-10-03 Nokia Corporation Mobile network message to email redirection
US20030123431A1 (en) * 2001-12-28 2003-07-03 Bertram Geck Methods and apparatus for providing internet messaging on the screen of a digital telephone
FR2834418B1 (en) * 2002-01-03 2004-02-27 Cit Alcatel METHOD FOR MANAGING TELEPHONE MESSAGES OF THE SMS TYPE IN A TELECOMMUNICATION NETWORK
FR2835143A1 (en) * 2002-01-21 2003-07-25 Cit Alcatel METHOD FOR SENDING AN "SMS" MESSAGE AND CORRESPONDING RADIO COMMUNICATION TERMINAL
TW569597B (en) * 2002-07-05 2004-01-01 Lite On Technology Corp Calling method using short message transmission on calendar group
DE10236082A1 (en) * 2002-08-07 2004-02-26 Deutsche Telekom Ag Short message service (SMS) via the public telephone system, requires use of programmed computer to provide FSK modulation of message signal
KR100861740B1 (en) * 2002-10-04 2008-10-06 인터내셔널 비지네스 머신즈 코포레이션 Method and apparatus for an e-commerce message using sms
CA2406880A1 (en) 2002-10-04 2004-04-04 Ibm Canada Limited-Ibm Canada Limitee Method and apparatus for an ecommerce message using sms
US6903743B2 (en) * 2002-10-16 2005-06-07 Motorola, Inc. Dynamic interactive animated screen saver
US7369865B2 (en) * 2002-10-17 2008-05-06 Manny Gabriel System and method for sending SMS and text messages
AU2002952173A0 (en) * 2002-10-18 2002-10-31 Nine Network Australia Pty Limited Mobile television reminder alert
GB0227978D0 (en) * 2002-11-29 2003-01-08 Jump Ltd Remote and real-time reporting of events at multi-locations
US20040127205A1 (en) * 2002-12-30 2004-07-01 Sanjeev Mahajan Over the air maintenance of mobile station telephone directories
KR100511300B1 (en) * 2002-12-31 2005-08-31 엘지전자 주식회사 Method for enhanced short message service
WO2005008984A1 (en) * 2003-07-14 2005-01-27 Moore Computer Consultants, Inc. Handheld device connectable to a mail server using wireless network and to a pc using local link syncronisation
EP1509049A1 (en) * 2003-08-20 2005-02-23 Accenture Global Services GmbH Methods and systems for providing information to mobile users over limited bandwidth
US7873353B2 (en) 2003-09-30 2011-01-18 Ianywhere Solutions, Inc. Method and system for accessing applications and data, and for tracking of key indicators on mobile handheld devices
US7146158B2 (en) * 2003-11-14 2006-12-05 Motorola, Inc. Method and apparatus for reformatting dialed numbers
ATE422798T1 (en) * 2003-11-26 2009-02-15 Nokia Corp FLEXIBLE MESSAGE DELIVERY SYSTEM
US20070143495A1 (en) * 2003-12-08 2007-06-21 Shai Porat Personal messaging systems
WO2005079084A1 (en) * 2004-01-13 2005-08-25 Nokia Corporation A method and device for interactive communication
US7162223B2 (en) * 2004-02-17 2007-01-09 Teamon Systems, Inc. System and method for notifying users of an event using alerts
US7043240B2 (en) * 2004-02-24 2006-05-09 Teamon Systems, Inc. Communications system with interface for enabling communication of alerts to mobile wireless communications devices
FI117313B (en) 2004-04-05 2006-08-31 Nokia Corp Message handling method in telecommunication system, involves obtaining capability data relating to client terminal and checking whether obtained data comprises upper-level application that is supported by client terminal
ES2547716T3 (en) 2004-04-14 2015-10-08 Mbalance Research B.V. Method to prevent the delivery of a junk message from the short message service
EP1767010B1 (en) * 2004-06-15 2015-11-11 Tekelec Global, Inc. Method, system, and computer program products for content-based screening of MMS messages
GB2416092B (en) * 2004-07-07 2007-03-14 Motorola Inc A cellular communication system, a network element and a method of operation therefor
US8135803B2 (en) 2004-08-23 2012-03-13 Ianywhere Solutions, Inc. Method, system, and computer program product for offline advertisement servicing and cycling
US7751836B2 (en) 2004-09-10 2010-07-06 Tekelec Methods, systems, and computer program products for short message service (SMS) spam filtering using e-mail spam filtering resources
US7774849B2 (en) * 2005-04-15 2010-08-10 Tekelec Methods, systems, and computer program products for detecting and mitigating denial of service attacks in a telecommunications signaling network
EP3654586B1 (en) 2005-04-18 2021-11-24 BlackBerry Limited Method for providing wireless application privilege management
US7945026B2 (en) 2005-05-27 2011-05-17 Telecommunications Systems, Inc. Voice over internet protocol (VoIP) E911 metro street address guide (MSAG) validation
US8913983B2 (en) 2005-05-27 2014-12-16 Telecommunication Systems, Inc. Voice over internet protocol (VoIP) E911 metro street address guide (MSAG) validation
KR100742363B1 (en) * 2005-10-07 2007-07-25 엘지전자 주식회사 Mobile terminal for united management of alert
US9161189B2 (en) 2005-10-18 2015-10-13 Telecommunication Systems, Inc. Automatic call forwarding to in-vehicle telematics system
US7860449B1 (en) * 2005-12-05 2010-12-28 Motricity, Inc. Method and system for delivering contextual content to a mobile device
US10290055B2 (en) * 2006-04-21 2019-05-14 Refinitiv Us Organization Llc Encoded short message service text messaging systems and methods
KR100814428B1 (en) 2006-06-29 2008-03-18 삼성전자주식회사 Short message processing method and apparatus
US10049077B2 (en) * 2006-06-30 2018-08-14 Intel Corporation Handheld device for elderly people
US7616131B2 (en) * 2006-10-16 2009-11-10 Motorola, Inc. Method and apparatus for allowing runtime creation of a user experience for a wireless device
US10255607B2 (en) * 2006-11-15 2019-04-09 Disney Enterprises, Inc. Collecting consumer information
US7912828B2 (en) * 2007-02-23 2011-03-22 Apple Inc. Pattern searching methods and apparatuses
US8179872B2 (en) 2007-05-09 2012-05-15 Research In Motion Limited Wireless router system and method
US8396928B2 (en) * 2007-09-21 2013-03-12 Smartbrief, Inc. Methods and systems for handling electronic message content for electronic communications devices
US8407296B2 (en) * 2007-09-24 2013-03-26 Smartbrief, Inc. Multiple and multi-part message methods and systems for handling electronic message content for electronic communications devices
GB2467073B (en) * 2007-11-16 2012-01-25 Ericsson Telefon Ab L M A terminal client and a client device for managing messages in a network infrastructure of a telecommunications system
US8311806B2 (en) 2008-06-06 2012-11-13 Apple Inc. Data detection in a sequence of tokens using decision tree reductions
US8738360B2 (en) * 2008-06-06 2014-05-27 Apple Inc. Data detection of a character sequence having multiple possible data types
US8489388B2 (en) 2008-11-10 2013-07-16 Apple Inc. Data detection
GB2470751A (en) * 2009-06-04 2010-12-08 Iq2 Ltd Delivering messages/content by determining if a target device is equipped with the appropriate application to enable the message/content to be conveyed.
US20110239146A1 (en) * 2010-03-23 2011-09-29 Lala Dutta Automatic event generation
WO2011142807A1 (en) 2010-05-10 2011-11-17 Telecommunication Systems, Inc. Cell-id translation in a location based system (lbs)
CN101867896A (en) * 2010-05-17 2010-10-20 中兴通讯股份有限公司 Method and system for controlling service
US8984271B2 (en) * 2010-06-07 2015-03-17 Protected Mobility, Llc User interface systems and methods for input and display of secure and insecure message oriented communications
US9602277B2 (en) 2010-06-07 2017-03-21 Protected Mobilty, Llc User interface systems and methods for secure message oriented communications
US9172680B2 (en) 2010-06-07 2015-10-27 Protected Mobility, Llc Systems and methods for enabling secure messaging, command, and control of remote devices, communicated via a short message service or other message oriented communications mediums
US9143324B2 (en) 2010-06-07 2015-09-22 Protected Mobility, Llc Secure messaging
US8924706B2 (en) 2010-11-05 2014-12-30 Protected Mobility, Llc Systems and methods using one time pads during the exchange of cryptographic material
US20120149339A1 (en) * 2010-12-10 2012-06-14 MobileIron, Inc. Archiving Text Messages
WO2012079648A1 (en) * 2010-12-17 2012-06-21 Telefonaktiebolaget L M Ericsson (Publ) Enabling a communication server to use msc-s related functions
US20130023279A1 (en) * 2011-07-19 2013-01-24 Tai Cheung Poon Systems and methods for handling time-related issues regarding sms communications
US8984273B2 (en) 2011-12-16 2015-03-17 Protected Mobility, Llc Method to provide secure multimedia messaging between peer systems
US9160719B2 (en) 2012-07-20 2015-10-13 Protected Mobility, Llc Hiding ciphertext using a linguistics algorithm with dictionaries
US9160698B2 (en) 2012-11-09 2015-10-13 The Rocket Science Group Llc Methods and systems for providing information relating to an event
KR101448593B1 (en) * 2013-01-15 2014-10-13 주식회사 네이블커뮤니케이션즈 Method of pushing web service and server performing the same
US9763067B2 (en) 2013-05-28 2017-09-12 Protected Mobility, Llc Methods and apparatus for long-short wave, low-high frequency radio secure message service
JP2023125712A (en) * 2022-02-28 2023-09-07 川崎重工業株式会社 Information processor

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1992014329A1 (en) * 1991-02-12 1992-08-20 Telenokia Oy A method for conveying information in a multi-service network
EP0642283A2 (en) * 1993-09-06 1995-03-08 Nokia Mobile Phones Ltd. Data transmission in a radio telephone network
WO1995012933A1 (en) * 1993-11-01 1995-05-11 Telefonaktiebolaget Lm Ericsson A message transmission system and method for a radiocommunication system
EP0689368A1 (en) * 1994-06-20 1995-12-27 Swisscom AG Message transmission arrangement in a mobile communication system
EP0748135A2 (en) * 1993-06-15 1996-12-11 Celltrace Communications Limited Telecommunications system
US5628051A (en) * 1993-01-15 1997-05-06 Nokia Telecommunications Oy Method for starting a message transmission in a mobile telephone network
US5635918A (en) * 1995-03-16 1997-06-03 Motorola, Inc. Method and apparatus for controlling message delivery to wireless receiver devices
WO1997020442A1 (en) * 1995-11-28 1997-06-05 Telefonaktiebolaget Lm Ericsson (Publ) Cellular telephone network having short message service interaction with other networks
US5652572A (en) * 1993-03-30 1997-07-29 Nec Corporation Radio pager capable of displaying fixed sentences
US5664004A (en) * 1995-01-13 1997-09-02 Nokia Telecommunications Oy Support of multiplicity of radio interfaces over an interface between a base station system and a mobile switch
EP0822728A2 (en) * 1996-07-30 1998-02-04 Lucent Technologies Inc. Two-way wireless cellular messaging system
US5781122A (en) * 1994-12-28 1998-07-14 Matsushita Electric Industrial Co., Ltd. Individual selective call receiving apparatus and method for displaying message
US5828313A (en) * 1995-07-21 1998-10-27 Nec Corporation Radio paging receiver for displaying a call message which includes illustration
US5920822A (en) * 1996-01-18 1999-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Formatting of short message service messages in a cellular telephone network
US5966663A (en) * 1997-01-14 1999-10-12 Ericsson Messaging Systems Inc. Data communications protocol for facilitating communications between a message entry device and a messaging center

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5577103A (en) * 1995-03-10 1996-11-19 Telefonaktiebolaget Lm Ericsson Method of providing service information to subscribers in a cellular telecommunications network using the short message service (SMS)
JP3167265B2 (en) * 1995-08-24 2001-05-21 三菱電機株式会社 Personal communication system

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5351235A (en) * 1991-02-12 1994-09-27 Telenokia Oy Method for relaying information in an integrated services network
WO1992014329A1 (en) * 1991-02-12 1992-08-20 Telenokia Oy A method for conveying information in a multi-service network
US5628051A (en) * 1993-01-15 1997-05-06 Nokia Telecommunications Oy Method for starting a message transmission in a mobile telephone network
US5652572A (en) * 1993-03-30 1997-07-29 Nec Corporation Radio pager capable of displaying fixed sentences
EP0748135A2 (en) * 1993-06-15 1996-12-11 Celltrace Communications Limited Telecommunications system
EP0642283A2 (en) * 1993-09-06 1995-03-08 Nokia Mobile Phones Ltd. Data transmission in a radio telephone network
WO1995012933A1 (en) * 1993-11-01 1995-05-11 Telefonaktiebolaget Lm Ericsson A message transmission system and method for a radiocommunication system
EP0689368A1 (en) * 1994-06-20 1995-12-27 Swisscom AG Message transmission arrangement in a mobile communication system
US5781122A (en) * 1994-12-28 1998-07-14 Matsushita Electric Industrial Co., Ltd. Individual selective call receiving apparatus and method for displaying message
US5664004A (en) * 1995-01-13 1997-09-02 Nokia Telecommunications Oy Support of multiplicity of radio interfaces over an interface between a base station system and a mobile switch
US5635918A (en) * 1995-03-16 1997-06-03 Motorola, Inc. Method and apparatus for controlling message delivery to wireless receiver devices
US5828313A (en) * 1995-07-21 1998-10-27 Nec Corporation Radio paging receiver for displaying a call message which includes illustration
WO1997020442A1 (en) * 1995-11-28 1997-06-05 Telefonaktiebolaget Lm Ericsson (Publ) Cellular telephone network having short message service interaction with other networks
US5920822A (en) * 1996-01-18 1999-07-06 Telefonaktiebolaget Lm Ericsson (Publ) Formatting of short message service messages in a cellular telephone network
EP0822728A2 (en) * 1996-07-30 1998-02-04 Lucent Technologies Inc. Two-way wireless cellular messaging system
US5966663A (en) * 1997-01-14 1999-10-12 Ericsson Messaging Systems Inc. Data communications protocol for facilitating communications between a message entry device and a messaging center

Cited By (162)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050017068A1 (en) * 1995-02-15 2005-01-27 Zalewski Thomas W. System and method of making payments using an electronic device cover with embedded transponder
US7155199B2 (en) 1995-02-15 2006-12-26 Nokia Mobile Phones Limited System and method of making payments using an electronic device cover with embedded transponder
US20020098855A1 (en) * 1996-09-27 2002-07-25 Peter Hartmaier Mobility extended telephone application programming interface and method of use
US7359720B2 (en) 1996-09-27 2008-04-15 Openwave Systems Inc. Mobility extended telephone application programming interface and method of use
US6400811B1 (en) 1997-07-30 2002-06-04 Internet2Anywhere Ltd. System and method for off-line notifying a network user
US6327479B1 (en) * 1997-09-22 2001-12-04 Nokia Networks Oy Procedure and system for the transmission of a short message in a telecommunication network
US6633318B1 (en) * 1997-12-26 2003-10-14 Samsung Electronics Co., Ltd. Screen saver having message management function and method therefor
US6263212B1 (en) * 1998-02-17 2001-07-17 Alcatel Usa Sourcing, L.P. Short message service center
US6341228B1 (en) * 1998-05-07 2002-01-22 Alcatel Method of parameterizing the display on mobile radio communications equipment co-operating with a subscriber identity module
US6292657B1 (en) * 1998-07-13 2001-09-18 Openwave Systems Inc. Method and architecture for managing a fleet of mobile stations over wireless data networks
US6895240B2 (en) 1998-07-13 2005-05-17 Openwave Systems Inc. Method and architecture for managing a fleet of mobile stations over wireless data networks
US6587684B1 (en) * 1998-07-28 2003-07-01 Bell Atlantic Nynex Mobile Digital wireless telephone system for downloading software to a digital telephone using wireless data link protocol
US6639941B1 (en) * 1998-12-04 2003-10-28 Nec Corporation Radio-signal transceiver
US6684087B1 (en) * 1999-05-07 2004-01-27 Openwave Systems Inc. Method and apparatus for displaying images on mobile devices
US6560456B1 (en) 1999-05-24 2003-05-06 Openwave Systems, Inc. System and method for providing subscriber-initiated information over the short message service (SMS) or a microbrowser
US20030211845A1 (en) * 1999-05-24 2003-11-13 Sunit Lohtia System and method for providing subscriber-initiated information over a microbrowser
US7783508B2 (en) 1999-09-20 2010-08-24 Numerex Corp. Method and system for refining vending operations based on wireless data
US8214247B2 (en) 1999-09-20 2012-07-03 Numerex Corp. Methods and system for managing vending operations based on wireless data
US8484070B2 (en) 1999-09-20 2013-07-09 Numerex Corp. Method and system for managing vending operations based on wireless data
US8126764B2 (en) 1999-09-20 2012-02-28 Numerex, Corporation Communication of managing vending operations based on wireless data
US20050002510A1 (en) * 1999-11-12 2005-01-06 Metro One Telecommunications, Inc. Technique for providing personalized information and communications services
US9749855B1 (en) 2000-01-13 2017-08-29 Citicorp Credit Services, Inc. (Usa) Method and system for conducting financial transaction and non-financial transactions using a wireless device
US20070053518A1 (en) * 2000-01-13 2007-03-08 Peter Tompkins Method and system for conducting financial and non-financial transactions using a wireless device
US8725632B2 (en) 2000-01-13 2014-05-13 Citicorp Development Center, Inc. Method and system for conducting financial and non-financial transactions using a wireless device
US20020046299A1 (en) * 2000-02-09 2002-04-18 Internet2Anywhere, Ltd. Method and system for location independent and platform independent network signaling and action initiating
US20020003882A1 (en) * 2000-03-21 2002-01-10 Barry Jones Method of, and means for, delivering information services over the air
US8032453B2 (en) 2000-04-14 2011-10-04 Citicorp Development Center, Inc. Method and system for notifying customers of transaction opportunities
US8145566B1 (en) 2000-04-14 2012-03-27 Citicorp Development Center, Inc. Method and system for notifying customers of transaction opportunities
US20070174448A1 (en) * 2000-04-14 2007-07-26 Arun Ahuja Method and system for notifying customers of transaction opportunities
US20020013711A1 (en) * 2000-04-14 2002-01-31 Arun Ahuja Method and system for notifying customers of transaction opportunities
US9418381B2 (en) 2000-04-14 2016-08-16 Citigroup Credit Services, Inc. (USA) Method and system for notifying customers of transaction opportunities
US6668059B1 (en) 2000-04-16 2003-12-23 Internet2Anywhere, Ltd. Telephone tuning and signaling system
US20030114140A1 (en) * 2000-05-30 2003-06-19 Jukka-Pekka Iivonen Billing for replies in a communication system
US6980792B2 (en) * 2000-05-30 2005-12-27 Nokia Corporation Billing for replies in a communication system
US6771981B1 (en) 2000-08-02 2004-08-03 Nokia Mobile Phones Ltd. Electronic device cover with embedded radio frequency (RF) transponder and methods of using same
WO2002032171A1 (en) * 2000-10-09 2002-04-18 Telstra New Wave Pty Ltd Message processing
US20050015443A1 (en) * 2000-10-10 2005-01-20 Alex Levine Personal message delivery system
US7243152B2 (en) 2000-10-20 2007-07-10 Universal Communication Platform Ag Method for transmitting short messages over the internet
US20040029598A1 (en) * 2000-10-20 2004-02-12 Karl Guggisberg Method for transmitting short messages over the internet
US7555537B2 (en) 2000-10-25 2009-06-30 Nokia Mobile Phones Ltd. Downloadable multimedia content and method for accounting
US20020087656A1 (en) * 2000-10-25 2002-07-04 Michael Gargiulo Downloadable multimedia content and method for accounting
US8060067B2 (en) 2000-10-27 2011-11-15 Cellemetry Llc Method and system for efficiently routing messages
US8903437B2 (en) 2000-10-27 2014-12-02 Numerex Corp. Method and system for efficiently routing messages
US7680505B2 (en) 2000-10-27 2010-03-16 Cellemetry, Llc Telemetry gateway
US8543146B2 (en) 2000-10-27 2013-09-24 Cellemetry, Llc Method and system for efficiently routing messages
US7343178B2 (en) * 2000-11-07 2008-03-11 Nec Corporation Mobile terminal, display switching method of mobile terminal, and recording medium for recording display switching program
US20020081997A1 (en) * 2000-11-07 2002-06-27 Masaaki Morishima Mobile terminal, display switching method of mobile terminal, and recording medium for recording display switching program
US20020123359A1 (en) * 2000-12-01 2002-09-05 Multiscience System Pte Limited Network for information transfer for mobile stations
US8346678B1 (en) 2000-12-29 2013-01-01 Citicorp Development Center, Inc. Method and system for conducting commerce over a wireless communication network
US8346677B1 (en) 2000-12-29 2013-01-01 Citicorp Development Center, Inc. Method and system for conducting commerce over a wireless communication network
KR20020060382A (en) * 2001-01-10 2002-07-18 이중한 Method and system of dual SMS number service
US20020156936A1 (en) * 2001-02-16 2002-10-24 Microsoft Corporation System and method for providing componentized transports and forms
US7191449B2 (en) * 2001-02-16 2007-03-13 Microsoft Corporation System and method for providing componentized transports and forms
US20020115424A1 (en) * 2001-02-20 2002-08-22 Bagoren Sevket Ilhan Replenishment of pre-paid wireless telephone accounts using short message service (SMS)
US6934529B2 (en) 2001-02-20 2005-08-23 Sevket Ilhan Bagoren Replenishment of pre-paid wireless telephone accounts using short message service (SMS)
US20070015501A1 (en) * 2001-10-26 2007-01-18 Jeffrey Wilson Telecommunications services apparatus
US20050070314A1 (en) * 2001-10-26 2005-03-31 Jeffrey Wilson Telecommunications services apparatus
WO2003053022A1 (en) * 2001-12-14 2003-06-26 Spl Innotech Pte Ltd. Messaging system
US20050075094A1 (en) * 2001-12-14 2005-04-07 Kundetkar Nandan Vinayakrao Messaging system
US20030114174A1 (en) * 2001-12-19 2003-06-19 Brian Walsh Mobile telephone short text messaging with message thread identification
US6816083B2 (en) 2002-02-04 2004-11-09 Nokia Corporation Electronic device with cover including a radio frequency indentification module
US7149537B1 (en) * 2002-02-12 2006-12-12 Cellco Partnership Method and system for generating a user-accessible internet-based mobile messaging log
US20040203606A1 (en) * 2002-03-13 2004-10-14 Novatel Wireless, Inc. Complete message delivery to multi-mode communication device
US7392039B2 (en) * 2002-03-13 2008-06-24 Novatel Wireless, Inc. Complete message delivery to multi-mode communication device
US20060059232A1 (en) * 2002-06-26 2006-03-16 Masato Yoshikawa Message transmission/reception system and method
US8046008B2 (en) * 2002-09-16 2011-10-25 Samsung Electronics Co., Ltd Method for transmitting and recording schedule using short message service
US20040196866A1 (en) * 2002-09-16 2004-10-07 Samsung Electronics Co., Ltd. Method for transmitting and recording schedule using short message service
US20120289202A1 (en) * 2002-11-07 2012-11-15 Research In Motion Limited Pseudo-interactive input processing in wireless environments
US20110117895A1 (en) * 2002-11-07 2011-05-19 Research In Motion Limited Pseudo-interactive input processing in wireless environments
US8250233B2 (en) * 2002-11-07 2012-08-21 Research In Motion Limited Pseudo-interactive input processing in wireless environments
US20160366570A1 (en) * 2002-11-07 2016-12-15 Blackberry Limited Pseudo-interactive input processing in wireless environments
US9894018B2 (en) 2002-11-18 2018-02-13 Facebook, Inc. Electronic messaging using reply telephone numbers
US20120198012A1 (en) * 2002-11-18 2012-08-02 Aol Inc. Enhanced buddy list using mobile device identifiers
US10033669B2 (en) 2002-11-18 2018-07-24 Facebook, Inc. Managing electronic messages sent to reply telephone numbers
US9356890B2 (en) * 2002-11-18 2016-05-31 Facebook, Inc. Enhanced buddy list using mobile device identifiers
US10389661B2 (en) 2002-11-18 2019-08-20 Facebook, Inc. Managing electronic messages sent to mobile devices associated with electronic messaging accounts
US9319356B2 (en) 2002-11-18 2016-04-19 Facebook, Inc. Message delivery control settings
US20040142708A1 (en) * 2003-01-17 2004-07-22 Hitachi, Ltd. Communication apparatus and communication system
US20090176506A1 (en) * 2003-01-31 2009-07-09 Qualcomm Incorporated Location based service (lbs) system, method and apparatus for triggering of mobile station lbs applications
US10237697B2 (en) 2003-01-31 2019-03-19 Qualcomm Incorporated Location based service (LBS) system, method and apparatus for triggering of mobile station LBS applications
US8938253B2 (en) * 2003-01-31 2015-01-20 Qualcomm Incorporated Location based service (LBS) system, method and apparatus for triggering of mobile station LBS applications
US8255877B2 (en) * 2003-03-06 2012-08-28 Gemalto Sa Method for managing the triggering of an application in a service terminal, particularly in a telecommunication terminal
US20100273521A1 (en) * 2003-03-06 2010-10-28 Gemplus Method for managing the triggering of an application in a service terminal, particularly in a telecommunication terminal
US20040266408A1 (en) * 2003-06-25 2004-12-30 Oracle International Corporation Mobile messaging concierge
WO2005015423A1 (en) * 2003-07-11 2005-02-17 Vazu, Inc. Method and system for transferring contact information to an sms-enabled wireless device
US9070118B2 (en) 2003-09-05 2015-06-30 Facebook, Inc. Methods for capturing electronic messages based on capture rules relating to user actions regarding received electronic messages
US10102504B2 (en) 2003-09-05 2018-10-16 Facebook, Inc. Methods for controlling display of electronic messages captured based on community rankings
US10187334B2 (en) 2003-11-26 2019-01-22 Facebook, Inc. User-defined electronic message preferences
US9084197B2 (en) 2004-01-21 2015-07-14 Numerex Corp. Method and system for interacting with a vehicle over a mobile radiotelephone network
US7880599B2 (en) 2004-01-21 2011-02-01 Numerex Corp. Method and system for remotely monitoring the operations of a vehicle
US8547212B2 (en) 2004-01-21 2013-10-01 Numerex Corporation Method and system for interacting with a vehicle over a mobile radiotelephone network
US8253549B2 (en) 2004-01-21 2012-08-28 Numerex Corp. Method and system for interacting with a vehicle over a mobile radiotelephone network
US7936256B2 (en) 2004-01-21 2011-05-03 Numerex Corp. Method and system for interacting with a vehicle over a mobile radiotelephone network
US8269618B2 (en) 2004-01-21 2012-09-18 Numerex Corp. Method and system for remotely monitoring the location of a vehicle
US20050176449A1 (en) * 2004-02-05 2005-08-11 Yahoo! Inc. Method and system for simplified access to alerts with a mobile device
US20050188320A1 (en) * 2004-02-24 2005-08-25 Bocking Andrew D. Method and system for managing unread electronic messages
US8291347B2 (en) * 2004-02-24 2012-10-16 Research In Motion Limited Method and system for managing unread electronic messages
US8255835B2 (en) * 2004-02-24 2012-08-28 Research In Motion Limited Method and system for managing unread electronic messages
US20090210823A1 (en) * 2004-02-24 2009-08-20 Research In Motion Corporation Method and system for managing unread electronic messages
US11599266B2 (en) 2004-02-24 2023-03-07 Blackberry Limited Method and system for managing unread electronic messages
US20050222754A1 (en) * 2004-03-30 2005-10-06 Naftali Meisler SMS vehicle information system
US8374638B2 (en) 2005-03-02 2013-02-12 Cisco Technology, Inc. System and method for providing a proxy in a short message service (SMS) environment
US20060199597A1 (en) * 2005-03-02 2006-09-07 Cisco Technology, Inc. System and method for providing a proxy in a short message service (SMS) environment
US7941165B2 (en) 2005-03-02 2011-05-10 Cisco Technology, Inc. System and method for providing a proxy in a short message service (SMS) environment
US20110165899A1 (en) * 2005-03-02 2011-07-07 Cisco Technology, Inc. System and Method for Providing a Proxy in a Short Message Service (SMS) Environment
WO2006126140A2 (en) * 2005-05-27 2006-11-30 Koninklijke Philips Electronics N.V. Method and apparatus for processing data
WO2006126140A3 (en) * 2005-05-27 2007-05-03 Koninkl Philips Electronics Nv Method and apparatus for processing data
US20060293937A1 (en) * 2005-06-24 2006-12-28 Mark Sohm System and method of wireless carpool scheduling
US20110034188A1 (en) * 2006-05-11 2011-02-10 Sony Ericsson Mobile Communications Ab Automatic spread of applications
WO2007131540A1 (en) * 2006-05-11 2007-11-22 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US20070265022A1 (en) * 2006-05-11 2007-11-15 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US7844287B2 (en) 2006-05-11 2010-11-30 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US20070265023A1 (en) * 2006-05-11 2007-11-15 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US8041373B2 (en) 2006-05-11 2011-10-18 Sony Ericsson Mobile Communications Ab Automatic spread of applications
US7680471B2 (en) 2006-05-17 2010-03-16 Numerex Corp. System and method for prolonging wireless data product's life
US8483748B2 (en) 2006-05-17 2013-07-09 Numerex Corp. Digital upgrade system and method
US8868059B2 (en) 2006-05-17 2014-10-21 Numerex Corp. Digital upgrade system and method
US8041383B2 (en) 2006-05-17 2011-10-18 Numerex Corporation Digital upgrade system and method
US20070270129A1 (en) * 2006-05-19 2007-11-22 Hui Luo Method and system for using a mobile terminal as a location-based reminder
US8126438B2 (en) * 2006-05-19 2012-02-28 Broadcom Corporation Method and system for using a mobile terminal as a location-based reminder
US7623526B2 (en) 2006-07-31 2009-11-24 Sony Ericsson Mobile Communications Ab Network interface for a wireless communication device
WO2008016722A3 (en) * 2006-07-31 2008-02-28 Sony Ericsson Mobile Comm Ab A network interface for a wireless communication device
WO2008016722A2 (en) * 2006-07-31 2008-02-07 Sony Ericsson Mobile Communications Ab A network interface for a wireless communication device
US11195163B2 (en) 2006-09-01 2021-12-07 Mastercard International Incorporated Methods, systems and computer readable media for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities
US20100151828A1 (en) * 2006-09-27 2010-06-17 Roebke Matthias Method for Services Identification for Convergent Messaging Systems
CN101563896B (en) * 2006-09-27 2012-10-17 T-移动国际股份公司 Method for service identification for convergent messaging systems
US8483664B2 (en) 2006-09-27 2013-07-09 T-Mobile International Ag Method for services identification for convergent messaging systems
WO2008037356A1 (en) 2006-09-27 2008-04-03 T-Mobile International Ag Method for service identification for convergent messaging systems
US9820078B2 (en) 2006-10-19 2017-11-14 Duc Anh Ngo Interactive system and process
US9002386B2 (en) * 2006-10-19 2015-04-07 Fruitful Technologies Pty Ltd. Interactive system and process
US20100197326A1 (en) * 2006-10-19 2010-08-05 Duc Anh Ngo interactive system and process
US20080163111A1 (en) * 2006-12-29 2008-07-03 Research In Motion Limited Streamlined entry of appointment record
US8543097B2 (en) 2007-02-06 2013-09-24 Numerex Corp. Service escrowed transportable wireless event reporting system
US8855716B2 (en) 2007-02-06 2014-10-07 Numerex Corp. Service escrowed transportable wireless event reporting system
US8265605B2 (en) 2007-02-06 2012-09-11 Numerex Corp. Service escrowed transportable wireless event reporting system
US20080255919A1 (en) * 2007-04-10 2008-10-16 Gorder Douglas P System and method for schedule notification
US9635488B2 (en) 2007-10-19 2017-04-25 Duc Anh Ngo Interactive system and process
US9191793B2 (en) 2007-10-19 2015-11-17 Duc Anh Ngo Interactive system and process
US20090112926A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Utilizing Presence Data Associated with a Resource
US20090112996A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Determining Presence Status of End User Associated with Multiple Access Terminals
US20090112997A1 (en) * 2007-10-25 2009-04-30 Cisco Technology, Inc. Utilizing Presence Data Associated with Web Item
WO2009118064A1 (en) * 2008-03-28 2009-10-01 Carryquote Ag Data communication of fixed size data packages
US20110069769A1 (en) * 2008-03-28 2011-03-24 Carryquote Ag Data communication of fixed size data packages
US20100041368A1 (en) * 2008-08-12 2010-02-18 Pradeep Kumar Methods, systems and computer readable media for electronically delivering a prepaid card to a mobile device
US8055286B1 (en) 2008-08-27 2011-11-08 Sprint Spectrum L.P. Modification of en-route message to add destination port number selected based at least in part on message originator
US10026076B2 (en) 2008-10-06 2018-07-17 Mastercard International Incorporated Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices
US8336762B1 (en) 2008-11-17 2012-12-25 Greenwise Bankcard LLC Payment transaction processing
EP2380125A2 (en) * 2008-12-31 2011-10-26 Vivotech, Inc. Methods, systems and computer readable media for redeeming and delivering electronic loyalty reward certificates using a mobile device
US20100174598A1 (en) * 2008-12-31 2010-07-08 Mohammad Khan Methods, systems and computer readable media for redeeming and delivering electronic loyalty reward certificates using a mobile device
EP2380125A4 (en) * 2008-12-31 2013-03-13 Mastercard International Inc Methods, systems and computer readable media for redeeming and delivering electronic loyalty reward certificates using a mobile device
WO2010097590A3 (en) * 2009-02-26 2010-10-21 Sepura Plc Transmission of encrypted short data messages in communications systems
US10992817B2 (en) 2009-03-18 2021-04-27 Mastercard International Incorporated Methods, systems and computer readable media for selecting and delivering electronic value certificates using a mobile device
US20100273450A1 (en) * 2009-04-27 2010-10-28 Papineau Scott A Apparatus and method for activating computer applications with sms messaging
US8213971B2 (en) * 2009-04-27 2012-07-03 Qualcomm Incorporated Apparatus and method for activating computer applications with SMS messaging
WO2010126831A1 (en) * 2009-04-27 2010-11-04 Qualcomm Incorporated Method and system for activating computer applications with sms messaging
US8408992B2 (en) 2011-03-10 2013-04-02 Riangelo Javier de Cuba SMS payment system having chargeback to subscriber telephone account
US8403741B2 (en) 2011-03-10 2013-03-26 Riangelo Javier de Cuba SMS messaging system accommodating variable entries for lotteries
ITMI20110394A1 (en) * 2011-03-14 2012-09-15 Leo Pillon SYSTEM AND METHOD FOR THE MANAGEMENT OF REMOTE DEVICE OPERATIONS.
US10009305B2 (en) * 2011-03-31 2018-06-26 Loment, Inc. Ubiquitous user control for information communicated among end user communication devices
US20120250593A1 (en) * 2011-03-31 2012-10-04 Majeti Venkata C Ubiquitous user control for information communicated among end user communication devices
US9767452B2 (en) 2011-11-03 2017-09-19 Mastercard International Incorporated Methods, systems, and computer readable media for provisioning and utilizing an aggregated soft card on a mobile device
US10546290B2 (en) 2011-11-03 2020-01-28 Mastercard International Incorporated Methods, systems, and computer readable media for provisioning and utilizing an aggregated soft card on a mobile device

Also Published As

Publication number Publication date
WO1998034422A2 (en) 1998-08-06
AU6214998A (en) 1998-08-25
US6125281A (en) 2000-09-26
EP0956719A2 (en) 1999-11-17
JP2001509981A (en) 2001-07-24
WO1998034422A3 (en) 1998-11-19

Similar Documents

Publication Publication Date Title
US6078820A (en) Real-time SMS application messaging using an SMSC-linked server
US6892074B2 (en) Selective message service to primary and secondary mobile stations
US7076528B2 (en) System and method for communicating messages between a host computer and a designated device
CN1745567B (en) Automatic notification of personal emergency contacts from a wireless communications device
US6941349B2 (en) System and method for pushing calendar event messages from a host system to a mobile data communication device
US6438585B2 (en) System and method for redirecting message attachments between a host system and a mobile data communication device
CN1716922B (en) Method and system for mobile device messaging
JP4123331B2 (en) Portable wireless communication terminal capable of multimedia communication with multimedia communication system and message transmission / reception method
US20030186722A1 (en) Method and device for real time GSM user device profile interrogation and registration
US20080046535A1 (en) System and Method for Pushing Information from a Host System to a Mobile Data Communication Device
US20100279723A1 (en) Method for transmitting short messages
US20100162388A1 (en) Wireless mobile device with automatic segregation of received messages for private and public access
US20030092454A1 (en) One step SMS message board and time management tools
CN1582011A (en) Methods and apparatus for alternative routing of text based messages on a cellular telephone network
US20050119019A1 (en) Method for searching for SMS message in a mobile terminal
NZ507072A (en) Method and arrangement for transferring information using an existing message based service in a digital network
US7254411B2 (en) Wireless data communication method
US8571065B2 (en) Method and apparatus for assigning a virtual address to and text-messaging to multiple text-capable destination entities
US20080049691A1 (en) Database management in a wireless communication system
US20040266408A1 (en) Mobile messaging concierge
EP1257097B1 (en) Method and system for routing SMS messages
EP1879405A1 (en) Method for appending a signature to a size limited text message
EP2020643A1 (en) System and method for acknowledging calendar appointments using a mobile device
EP1655932A2 (en) Portable cellular phone, portable cellular phone system, message format controlling method and message format controlling program
EP1571793A2 (en) Method and device for managing stored messages

Legal Events

Date Code Title Description
STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12