WO2009149444A1

WO2009149444A1 - Free short messaging service/multimedia messaging service system and related method of operating the same

Info

Publication number: WO2009149444A1
Application number: PCT/US2009/046591
Authority: WO
Inventors: Ricky Sy Chan; Vince Domninc Tuano Yamat; Rickman Manzano Nono
Original assignee: Feedtext, Inc.
Priority date: 2008-06-06
Filing date: 2009-06-08
Publication date: 2009-12-10

Abstract

The present invention relates to a system and method for sending Short Messaging Service ("SMS") or Multimedia Messaging Service ("MMS") messages free of charge by a prepaid mobile phone service user with no stored value credits (sender with zero credit) to an intended recipient from the same or another mobile phone service operator The method involves a network of system-generated virtual mailboxes adapted to receive and store one or more SMS/MMS messages sent by senders with zero credit and a messaging application that identifies, parses and stores said messages into the virtual mailboxes, adds the sender to the recipients subscription table tagged with a unique number that serves as an identification, notifies the intended recipient of messages in the system-generated virtual mailbox waiting to be retrieved, allows the intended recipient to retrieve said messages for a fee, and allows the retriever to subscribe to the sender via his subscription table

Description

FREE SHORT MESSAGING SERVICE/MULTIMEDIA MESSAGING SERVICE SYSTEM AND RELATED METHOD OF OPERATING THE SAME

RELATED APPLICATION

This application claims the benefit of priority to U.S. Provisional Patent Application Number 61/129,138 entitled "Mobile Phone Text Message System and Method," that was filed on June 6, 2008, the full contents of which are incorporated in this application by reference.

TECHNICAL FIELD

The subject invention is in the field of mobile phone communications, and more particularly is directed to a system and method for sending Short Messaging

Service ("SMS") or Multimedia Messaging Service ("MMS") messages free of charge by prepaid mobile phone service users with no stored value credits ("sender with zero credit") to their intended recipients.

BACKGROUND OF THE INVENTION

SMS/MMS is a feature available in most mobile phones that allows mobile phone users to send and receive text messages or messages with rich content to other mobile phones, hi order to send an SMS/MMS message, the sender typically has to pay a messaging fee to a mobile phone service operator. The recipient, on the other hand, does not need to pay any messaging fee in most markets to receive the SMS/MMS messages.

In markets where prepaid mobile phone service is the preferred form of mobile phone service subscription due to the economic or other reasons, the prevalent scenario is that of a prepaid mobile phone service user with no stored value credits (a "zero credit" or "no load" scenario). When a prepaid mobile phone service user reaches zero credit, his/her ability to send a SMS/MMS messages is automatically disabled by the mobile phone service operator. To restore SMS/MMS messaging capability, the prepaid mobile phone service user with zero credit must "reload" or "top up" his/her stored value credits. This situation can be highly inconvenient in cases where the prepaid mobile phone service user with zero credit needs to send an urgent SMS/MMS message but cannot do so due to a zero credit or no load scenario.

In recent times, mobile phone service operators have proposed various solutions to address the zero credit or no load scenario, the representative variants including:

(a) GLOBE TELECOM'S "CALL AND TEXT COLLECT" PROMO

Under Globe Telecom's ("GLOBE") "Call and Text Collect" promo, GLOBE postpaid subscribers may choose to receive voice calls and SMS/MMS messages from prepaid mobile phone service users within the GLOBE network even after these users have reached zero credit.

The promo involves an opt-in procedure where the GLOBE postpaid subscriber "enrolls" a maximum of five (5) GLOBE prepaid mobile phone service users from whom he or she would like to receive voice calls and SMS/MMS messages during a zero credit or no load scenario. By opting-in, the GLOBE postpaid subscriber agrees to shoulder the cost of the voice calls made and the SMS/MMS messages sent by the enrolled GLOBE prepaid mobile phone service users during a zero credit or no load scenario.

(b) GLOBE TELECOM'S "TEXT BACK MO, LBRE KO" ("I'LL PAY FOR YOUR SMS REPLY") PROMO

Under GLOBE's "Text Back Mo, Libre Ko" ("I'll Pay for Your SMS Reply") promo, GLOBE mobile phone service users, whether postpaid or prepaid, can send another GLOBE mobile phone service user a SMS message and, by paying an add-on rate messaging fee for his/her original message, shoulder the cost of the recipient's reply.

(c) SMART COMMUNICATIONS ' "ASK-A-LOAD" PROMO

Under Smart Communications' ("SMART") "Ask-a-Load" promo, SMART prepaid mobile phone service users with zero credit may request another SMART mobile phone service user, whether postpaid or prepaid, to transfer stored value credits or to load to his or her account. This promo requires the requesting party to dial a SMART access code followed by the requested party's 11 -digit mobile phone identification number. SMART then sends the requested party an SMS message notifying him or her that the requesting party requests that he or she transfers a specified amount of stored value credits or load to the requesting party's account. The requested party can then transfer the requested amount of stored value credits or load to the requesting party's account by sending SMS instructions to SMART if he or she accepts the request, or can simply ignore the same. While sending a request for stored value credit or load transfer is free of charge, a requesting party can only send three (3) requests per day. (d) CHKKA MESSENGER AND YAHOO MESSENGER

CHIKKA and YAHOO's Instant Messaging Service ("BVI") allow users to send free SMS messages to any mobile phone service user free of charge. SMS messages sent via CHIKKA and YAHOO DVI is immediately transmitted to the recipient's mobile phone. The recipient of the SMS message is not billed for receiving SMS messages but pays a premium messaging fee to his or her mobile phone service operator if he or she opts to reply to a free SMS message.

CHIKKA and YAHOO IM users can send up to three (3) personal computers ("PC") to mobile phone SMS messages only without the recipient replying to any message. If the recipient of the messages does not reply after three (3) personal computers ("PC") to mobile phone SMS messages have been sent, the CHIKKA and YAHOO EvI sender will not be able to send further messages to the intended recipient.

All of the foregoing attempts to address the zero credit or no load situation (except for CHIKKA and YAHOO's PC to mobile phone SMS model) require the sender to have a minimum stored value credit or load balance in their account in order to function. Thus, they all fail to completely solve the zero credit or no load problem scenario. The present invention was developed precisely to address the shortcomings of these previous attempts and truly enable prepaid mobile phone service users with absolutely zero credit loads to send SMS/MMS messages to other mobile phone users. The present invention achieves the intended objectives by allowing a prepaid mobile phone service user with zero credit to send an SMS/MMS message to his or her mobile phone service operator. A messaging application running on an application server receives, identifies, parses and stores the SMS/MMS message into a network of system-generated virtual mailboxes. The application then notifies the intended recipient that there are SMS/MMS messages from a sender with zero credit in his or her system-generated virtual mailbox waiting to be retrieved, allows the intended recipient to retrieve said SMS/MMS messages stored in his or her virtual mailbox for a fee, typically at premium messaging rates, and notifies the sender with zero credit that his or her SMS/MMS message was retrieved by the intended recipient. The present invention thus eliminates the need for the sender of the SMS/MMS to pay the messaging fee for the outgoing SMS/MMS message, which is shouldered by the recipient at a premium if he opts to do so. This invention can also be used in any other type of mobile messaging system (e.g., multimedia, video, email, voice and/or any other type of message via any available media).

SUMMARY OF THE INVENTION

The above noted problems, which are inadequately or incompletely resolved by the prior art are completely addressed and resolved by the present invention.

A preferred aspect of the present invention is a system for sending Short Messaging Service ("SMS") or Multimedia Messaging Service ("MMS") messages, free of charge, by at least one prepaid mobile phone service user with no stored value credits ("sender with zero credit") to an intended recipient, comprising a mobile phone service operator of the sender with zero credit; a mobile phone service operator of the intended recipient; a network of system-generated virtual mailboxes adapted to receive and store a plurality of SMS/MMS messages; and a messaging application that identifies, parses and stores SMS/MMS messages sent by said senders with zero credit into said virtual mailboxes, wherein said system (a) notifies the intended recipient that there are SMS/MMS messages from a sender with zero credit in a system-generated virtual mailbox waiting to be retrieved, (b) allows the intended recipient to retrieve said SMS/MMS messages stored in a system-generated virtual mailbox, and (c) notifies the sender with zero credit that his SMS/MMS message was retrieved by the intended recipient. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a network diagram of a typical SMS/MMS messaging service. FIG. 2 is a network diagram of a typical embodiment of the present invention.

FIGS. 3 A and 3B are network diagrams illustrating the process flow for sending SMS/MMS messages, notifications and retrieval of messages in accordance with the present invention.

FIG. 4 is a network diagram illustrating the message flow for sending SMS/MMS messages, notifications and retrieval of messages in accordance with the present invention. FIG. 5A and 5B are network diagrams illustrating the process flow for sending

SMS/MMS messages, notifications and retrieval of messages from two different mobile phone operators in accordance with the present invention.

FIG. 6 is a sequence diagram for sending SMS/MMS messages to another mobile phone operator in accordance with the present invention. FIG. 7 A and 7B is sequence diagram for retrieving SMS/MMS messages and subscribing to user in accordance with the present invention.

FIG. 8 is a basic flow chart on how to register to the service in accordance with the present invention.

FIG. 9 is a basic flow chart on how to send a SMS/MMS message to a mobile number in accordance with the present invention.

FIG. 10 is a basic flow chart on how to send a SMS/MMS message via the nickname saved on the virtual address book in accordance with the present invention.

FIG. 1 IA and 1 IB are basic flow chart on how to retrieve a SMS/MMS message and subscribing to a user in accordance with the present invention. FIG. 12 is a basic flow chart on how to get the list of available SMS/MMS messages stored in the virtual inbox of a user in accordance with the present invention. FIG. 13 A, 13B and 13C are basic flow chart on how to add a contact to the virtual address book, editing contacts mobile number in the virtual address book and editing contacts nickname in accordance with the present invention.

FIG. 14 is a basic flow chart on how to delete contacts information in accordance with the present invention.

FIG. 15A and 15B are basic flow chart on how to block and unblock a number from sending SMS/MMS message in accordance with the present invention.

FIG. 16 A, 16B and 16C are basic flow chart on how to opt-out on the service, how to activate virtual inbox and unsubscribing from a user in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

As illustrated in FIG. 1, a known method of sending standard SMS/MMS messages is shown. Such a system generally includes an operator cell site and an operator Short Messaging Service Center ("SMSC")/Multimedia Messaging Service Center ("MMSC"). The operator SMSC/MMSC is responsible for routing and billing SMS/MMS messages. In FIG. 1, a sender sends a standard SMS/MMS message to another mobile phone user. The sender is charged a standard rate while the recipient of the message is not billed for receiving the message.

It is to be noted that FIG. 1 is representative of only one of many possible SMS/MMS systems and configurations, and is therefore exemplary only.

Furthermore, it should be understood that the present invention is also applicable to many other types of messaging systems.

FIG. 2 illustrates, by comparison, a network diagram of a typical embodiment of the present invention where an SMS or MMS Gateway ("SMSGW/MMSGW") interfaces via Hypertext Transfer Protocol ("HTTP"), Computer Interface Message Distribution 2 ("CMD2"), Universal Computer Protocol ("UCP") or any other socket connections to an operator SMSC/MMSC. The connection between the SMSGW/MMSGW and operator SMSC/MMSC can be via the internet or via a local Ethernet connectivity. The SMSGW/MMSGW is also connected to the messaging application via a typical Transmission Control Protocol/Internet Protocol ("TCP/IP") connection. The messaging application shown in Fig. 2 validates all message requests before storing them in the intended recipient's mailbox. Once stored, the messaging application will send an SMS/MMS notification to the SMSGW/MMSGW for delivery to the intended recipient informing him/her that there is a message in his/her mailbox waiting for retrieval.

As shown in further detail in FIGS. 3 A 3B and 4 network diagrams, illustrations of the process flow for sending SMS/MMS messages, notifications and retrieval of messages in accordance with the present invention are depicted.

In a preferred embodiment of the present invention, as shown in FIG. 3 A, the sender with zero load or credit sends an SMS/MMS message to an access code consisting of the 11 -digit mobile number of the recipient followed by the sender's message. The operator SMSC/MMSC sends the SMS/MMS message to the SMSGW/MMSGW for validation and the message is processed by the messaging application. The application's parsing unit extracts the content of the message according to a presetting keyword and stores the same in a system- generated virtual mailbox assigned to the intended recipient. The application's notifying unit meanwhile informs the intended recipient that there is a new SMS/MMS message in his/her mailbox sent by a sender with zero credit.

As shown in FIG. 3B, the recipient has the option to download the message stored in his/her mailbox or may simply ignore it. Should he/she opt to download the message, the recipient sends a confirmatory SMS/MMS message to an access code consisting of an action word such as "GET" followed by the message number. Upon receipt of the SMSGW/MMSGW of the request, the messaging application parses the data and identifies the requestors Mobile Station ISDN Number ("MSISDN"). The application then looks for the mailbox attached to the MSISDN and retrieves the message number requested. The message is forwarded to the requestor and, upon receipt of the message, the application's notifying unit sends an SMS/MMS notification to the sender that the message was retrieved by its intended recipient.

FIG. 4 provides a network diagram illustrating the message flow for sending SMS/MMS messages, notifications and retrieval of messages in accordance with the present invention. A user from one carrier sends a message to other networks, and a notification message is received by the intended recipient. Thereafter, the recipient has the option to retrieve the message or not. If the recipient opts to retrieve the message, he/she will receive the message sent to him.

Network diagrams illustrating the process flow for sending SMS/MMS messages, notifications and retrieval of messages to and from two (2) different mobile phone operators, in accordance with the present invention, are illustrated in FIGS. 5A and 5B.

In a typical embodiment, the sender with zero load or credit, as noted in FIG. 5 A, sends an SMS/MMS message to an access code consisting of the country code + area code + the mobile number of the recipient followed by the sender's message.

The operator SMSC/MMSC sends the SMS/MMS message to the SMSGW/MMSGW for validation and the message is processed by the messaging application. The application's parsing unit extracts the content of the message according to a presetting keyword. In this case the system extracts the mobile number of the intended recipient by parsing the country code, mobile number and message and stores the same in a system-generated virtual mailbox assigned to the intended recipient. The application's notifying unit meanwhile informs the intended recipient that there is a new SMS/MMS message in his/her mailbox sent by a sender with zero credit.

The recipient as shown in FIG. 5B has the option to download the message stored in his/her mailbox or may simply ignore it. Should he/she opt to download the message, the recipient sends a confirmatory SMS/MMS message to an access code consisting of an action word such as "READ" followed by the message number. Upon receipt of the SMSGW/MMSGW of the request, the messaging application parses the data and identifies the requestors Mobile Station ISDN Number ("MSISDN") which includes the country code. The application then looks for the mailbox attached to the MSISDN and retrieves the message number requested. The message is then forwarded to the requestor.

The details of the sequence of how the system handles messages sent from a mobile phone operator and retrieved by another mobile phone subscriber from another mobile phone operator, and subscribing to a user, with greater emphasis on billing procedures, are shown in FIGS. 6, 7 A and 7B. The precondition here is to set the SMSC/MMSC to allow users with zero loads to send SMS/MMS messages to a specially designated access code. Another precondition is that billing should be based on Message Termination or only those that have been successfully retrieved or downloaded by the recipient. In a typical embodiment, as shown in FIG. 6, the sender from mobile operator

A with zero load or credit sends a SMS/MMS message to an access code consisting of the country code + area code + the mobile number of the recipient followed by the sender's message. The SMSC/MMSC of mobile operator A will send the request to the SMSGW/MMSGW of the application provider. The SMSGW/MMSGW will then validate the request and send the request to the Application Server, validate the request, process and store the message in the system-generated virtual mailbox assigned to the intended recipient. After storing the message, the virtual mailbox will then send a return response to the application server and the application notifying unit will send a notification message to the corresponding SMSGW/MMSGW assigned to mobile phone operator B. The SMSGW/MMSGW B interfacing with the

SMSC/MMSC of mobile operator B will then validate and send the notification request and send the notification message to the SMSC/MMSC of mobile operator B. The SMSC/MMSC of mobile operator B then validates the notification message request and sends the notification message to the intended recipient. The message termination fee for the notification messages are either charged standard rates of the receiving mobile operator or it can be tagged at zero tariff.

As shown in the flow diagram of FIG. 7 A, upon receipt of the notification message, the recipient has the option to download the message stored in his/her mailbox or may simply ignore it. Should he/she opt to download the message, the recipient sends a confirmatory SMS/MMS message to an access code of the home mobile phone operator consisting of an action word such as "READ" followed by the message number. Upon receipt of the SMSGW/MMSGW B of the request, the messaging application parses the data and identifies the requestors Mobile Station ISDN Number ("MSISDN") which includes the country code + area code. The application then looks for the mailbox attached to the MSISDN and retrieves the message number requested. The message is then sent to the intended recipient's mobile phone via access code + any unique number. The unique number will serve as the identifier for the sender. Upon receipt of the message the recipient will be billed, usually at premium or increased SMS rate. Once billed the SMSC/MMSC B will send a delivery receipt to the SMSGW/MMSGW B to trigger that the message has been retrieved. SMSGW/MMSGW B then sends the receipt to the application server to process the request.

Similarly, as shown in FIG. 7B, a message retrieved will be received via the access code + a crossed sell message that teaches how to subscribe to the specific sender. On the crossed sell message, a unique number will be presented to identify the sender. An intended recipient has the option to subscribe or not subscribe to the sender. If the user chooses to subscribe, he/she just has to reply to the receive message. He/she can reply YESΛ7OK/ON/SUBSCRIBE + unique number indicated in the crossed sell message. Upon receipt of the SMSGW/MMSGW B of the request, the messaging application parses the data and identifies the requestors Mobile Station ISDN Number ("MSISDN") which includes the country code + area code. The application then validates the process and the request. Once validated, the user will be subscribed to the intended user and a confirmation message will be sent to the subscriber.

FIG. 8 is a basic flow chart showing how to register to the service in accordance with a preferred embodiment of the present invention. A user registers to the service via the correct syntax (for example: REG First Name/Last Name/ Address/ Age/Gender) and is sent to the access number. The application will check whether the MSISDN is already a user or not. If the user is already registered the application will sent a notification message notifying the user that he/she is already registered. If the user is not yet registered the registration will be parsed and validated. The application will also check whether the registration syntax are correct. It will first check if the registration syntax is complete or not, such that if it is not complete, the application will notify the user by sending error notification message. If the syntax is complete, then first name syntax will be checked. The application will check if the First Name is within the 15 characters limit. After checking, the application will send a notification error message if the syntax is wrong or will then check the Last Name syntax if the First Name syntax is correct. Like the First Name syntax, the Last Name syntax is checked. The address will not be checked if properly done since address consists of alpha-numeric characters. Age syntax are then checked and validated. Acceptable age range may be from 5 to 99. The Gender syntax is then checked if properly addressed. In standard notation, M or Male for males, and F or Female for females.

Once the system validated the registration, information will be stored to the applications database. A notification message will then be sent to the registrant upon successful registration. In a preferred embodiment, the registration process is free and even zero load subscribers can register. Users can registers even if the only supplemented information is the First Name. Through use of these two rules, users can easily register with the service. As is typical in the use of any service, users need to register before using the service.

FIG. 9 is a basic flow chart showing how to send a SMS/MMS message to a mobile number in accordance with the present invention. Zero Load Subscribers can send messages by sending the proper syntax to the access code. To send a SMS/MMS message, a user must send an SMS/MMS message to an access code consisting of the country code + area code + the mobile number of the recipient followed by the sender's message. The system then checks to see if the syntax is correctly provided by the user. The system will check if the MSISDN of the intended recipient is a valid MDSf. Ifthe MIN is not valid a notification message will be sent to the sender. If the syntax is correct, the system will check ifthe sender is a registrant of the service. If the user is not registered a notification message will be sent to the user notifying him/her that his/her message is not sent because he/she is not registered to the service.

Ifthe user is registered, the system will check to see if he/she is not blocked by the intended recipient. If he/she is blocked, an error notification message will be sent to the user. If he/she is not blocked by the intended recipient the system will check ifthe recipient has, by way of example, 30 unread or not retrieved messages on his/her virtual inbox. Ifthe recipient already has, by way of example, 30 unread / no retrieved messages on his/her virtual inbox, then the sender will be notified and the message will not be sent. As shown in FIGS. 9 and 10, the system will next check the recipient's virtual inbox to see if sender has 3 unread / not retrieved messages on recipient's virtual inbox. If the sender has 3 unread / not retrieved messages sent to recipients virtual inbox, the message sent will not be processed and an error notification message will be sent to the sender. Next the system checks the recipient's virtual address book to see if sender's MIN is stored to the recipient's virtual address book with NICK. If sender's MIN is stored at the recipient address book, the system will process the message and send the notification message to the recipient with the sender's nickname on it. Alternatively, the notification message sent to the recipient will be the sender's registered First Name. Once the message notification is sent to the intended recipient, the system will check if sender is already added to the intended recipient's subscription table. If sender already exist, the process will end. If the sender does not exist, the sender's information will be saved at the recipient's subscription table and will assign a unique number to identify the sender. FIG. 10 is a basic flow chart on how to send a SMS/MMS message via the nickname saved on the virtual address book in accordance with the present invention. Zero Load Subscribers can send messages by sending the proper syntax to the access code. To send a SMS/MMS message user must send an SMS/MMS message to an access code consisting of the nickname (saved at the user's virtual address book) of the recipient followed by the sender's message. As similarly illustrated in FIG. 9, the system will check to see if the syntax is correctly completed by the user. The system will check if the sender is a registrant of the service. If the user is not registered, a notification message will be sent to the user notifying him/her that his/her message is not sent because he/she is not registered to the service. If the user is registered, then the system will check his/her virtual address book. The system will check if the nickname supplemented does exist within the sender's virtual address book. If the nickname doesn't exist, an error notification message will be sent to the sender. If the nickname does exist, then the system will check if he/she is not blocked by the intended recipient. If he/she is blocked, error notification message will be sent to the sender. If he/she is not blocked by the intended recipient, the system will check to see if the recipient has, by way of example, 30 unread / not retrieved messages on his/her virtual inbox. If the recipient already has, by way of example, 30 unread / not retrieved messages on his/her virtual inbox, then the sender will be notified about it and the message will not be sent. If the condition is met, then the system will check the recipients virtual inbox to see if sender has, by way of example, 3 unread / not retrieved messages on recipient's virtual inbox.

If the sender has, by way of example, 3 unread / not retrieved messages within recipients virtual inbox, the message sent will not be processed and an error notification message will be sent to the sender. If the condition is satisfied, then the system will check the recipient's virtual address book to see if sender's MIN is stored to the recipient's virtual address book with NICK. If sender's MIN is stored at the recipient address book, the system will process the message and send the notification message to the recipient with the sender's nickname on it. If the MIN is not stored, the notification message sent to the recipient will be the sender's registered First Name. Once the message notification is sent to the intended recipient, the system will check to see if sender is already added to the intended recipient's subscription table. If sender already exist, the process will end. If the sender does not exist, then the sender's information will be saved at the recipient's subscription table and will assign a unique number to identify the sender.

FIG. 1 IA is a basic flow chart showing how to retrieve a SMS/MMS message in accordance with the present invention. The intended recipient will receive a notification message regarding the message sent by a user. He then has an option to retrieve or download the message. To download the SMS/MMS message sent to him, a user must send an SMS/MMS message to an access code consisting of the "READ" and the corresponding message number. The system will check the syntax to see if it is correct. If the syntax sent is invalid, the system will send an error message to the user. If the syntax sent is valid, then the system will check if the user is already opted out to the service. If he is not enrolled or already opted out to the service, then he will receive an error message. If he is enrolled to the service, the system will check his virtual inbox to see if his/her virtual inbox is empty. If empty, an error message will be sent to the user. If not empty, then the system will check if the message number sent is correct. If the message number is invalid, an error message will be sent to the user. If the message number is valid, then the system will process the message.

The message format will vary depending on whether the sender's nickname is saved to recipient's virtual address book. A user must have sufficient credits to be able to retrieve a message. An instruction on how to subscribe to the sender may be crossed sold with the retrieved message.

FIG. 1 IB is an illustrative basic flow chart showing how to subscribe to a user. Upon receipt of the retrieved messages, users can subscribe by replying YES/Y/OK/ON/SUBSCRIBE + the unique number indicated in the crossed sell message. The unique number is the identification that refers to the sender. Upon receipt of the reply, the system will check if the user sent the correct syntax. If the system returns invalid syntax, an error message is sent to the user. If the system returns valid, the system will check if the unique number supplemented is existing in the recipient's subscription table. If the number doesn't exist, an error message is sent to the subscriber. If the number does exist, the system will check if the subscriber is already subscribe or not. If the user is already subscribed, an error message is then sent. If the user is not subscribed, then the subscriber will be subscribed to the user upon successful subscription, and a corresponding message confirmation will be sent to the subscriber. In further detail, FIG. 12 shows a basic flow chart on how to get the list of available SMS/MMS messages stored in the virtual inbox of a user in accordance with the present invention. Users can check if they have a message on their virtual inbox or to check what are the numbers of the messages on their virtual inbox. To get the list of messages on the virtual inbox, user must send a SMS message containing the syntax "INBOX" to the access code. Upon receipt of the message, the system will check if the user is an existing user of the service. If not, the system will check the user's virtual inbox. If the user is not an existing user, the system then will check if the user already opted out to the service. If opted out, an error message will be sent to the user. If they have not opted out, the system will check the user's virtual inbox. The system will then check if the user's virtual inbox is empty. If it is empty, then an error message is sent to the user. If it is not empty, then the system will send a SMS/MMS message stating that user has still X numbers of message on his/her virtual inbox.

FIG. 13 A, 13B and 13C are basic flow charts showing how to add a contact to the virtual address book, editing contacts mobile number in the virtual address book, and editing contacts nickname in accordance with the present invention. More specifically, FIG. 13 A shows how the user can add contact on his/her virtual address book. For a user to add a contact he/she must send a SMS message with the proper syntax to the access code. To add a contact in the virtual address book, a user must send ADD + contacts nickname + contacts mobile number to access number. The system will then check if the syntax sent is correct and valid. If the nickname already exist, the system will send an error message. If the nickname does not exist, then the system will check the 15 character limit for nickname. If the nickname syntax is correct the mobile number will be checked if the mobile number already exists or is not valid. A corresponding error message will be sent for if there are errors found. Once check and validated, the system will save the user's contact to his/her virtual address book.

Similarly, FIG. 13B shows how the user can change his/her contacts mobile number in his/her virtual address book. For a user to edit an existing contact to his/her virtual address book, he/she must send a SMS message with the proper syntax to the access code. To edit a contacts mobile number, he/she must send CNUM + contacts nickname + the new mobile number to access code. The system will then check if the syntax is properly done. The system will first check if the nickname exists. A corresponding error message will be sent if the nickname does not exist. The system will then check if the mobile number supplemented already exists. A corresponding error message will be sent if the mobile number given does exist on his/her address book. If the mobile number given does not exist, the new number for the said contact will be edited.

FIG. 13C illustrates how the user can change his/her contacts nickname in his/her virtual address book. For a user to edit an existing contact to his/her virtual address book, he/she must send a SMS message with the proper syntax to access code. To edit a contacts nickname, he/she must send CNICK + old nickname + new nickname to access code. The system will check if the syntax sent are correct and will process the request. The system will first check if the old nickname given exists. A corresponding error message will be sent if the given old nickname does exist or not. Alternatively, the system will check if the new nickname give is already saved on his/her virtual address book. Once validated, the request will be processed, and the edited nickname will be saved to his/her virtual address book.

FIG. 14 is a basic flow chart showing how to delete contacts information in accordance with a preferred embodiment of the present invention. For a user to delete a contact saved to his/her virtual address book, he/she must send a SMS message to access code with the proper syntax. To delete a contact, he/she must send DEL + mobile number of the contact to be deleted, and send it to access code. Once the request is sent the system will process it and will check to see if the syntax is properly done. A corresponding error message will be sent to the user if the syntax is not properly done. The system will then check to see if the mobile number exists. If the mobile number does not exist, an error message will be sent to the user. If the mobile number does exist, then the request will be processed and the contact will deleted from his/her virtual address book.

FIG. 15A and 15B are basic flow charts showing how to block and unblock a number from sending SMS/MMS message in accordance with the present invention. FIG 15 A shows how a user can block a mobile number from sending him free

SMS/MMS messages. To block a mobile number a user must send a SMS message to access code. To block a user must send a SMS message with the following syntax, BLOCK + mobile number to be blocked, and send it to access code. The system will check the syntax if valid and correct. A corresponding error message will be sent if the syntax is incorrect. Alternatively, the system will check if the mobile number is valid. Once the system validates the parameters, the request will be processed and the mobile number supplemented will be blocked. The user will not get any SMS/MMS message to the user.

Conversely, FIG. 15B shows how a user can unblock a blocked user from sending him/her free SMS/MMS messages. To unblock, the user must send a SMS message to access code. To unblock, the user must send the syntax UNBLOCK + the mobile number to be unblocked, to access code. The system will check if the syntax is correct. Once checked, the system will check to see if the mobile number is valid. A corresponding error message will be sent to the user. If the mobile number is valid, the system will then check if the mobile number is on the users block list. If the mobile number is not present on the block list, an error message will be sent to the user. If the mobile number is present on the block list, then the request will processed and the mobile number will be unblocked. Mobil numbers unblocked can now send free SMS/MMS messages to the user.

Lastly, FIG. 16A and 16B are basic flow charts showing how to opt-out of the service, and how to activate virtual inbox in accordance with the present invention. More specifically, FIG. 16A shows how to opt-out to the service. For a user to opt-out from the service he must send a SMS message to access code. To opt-out, he must send STOP to access code. The system will check if the user is registered to the service. A corresponding error message will then be sent to the user. If the request is processed, the user will be opted-out to the service. Users opted out of the service will not be able to receive SMS/MMS messages. This will also disable the virtual inbox of the user.

FIG. 16B shows how to activate a virtual inbox which has been previously deactivated by the user. To activate the virtual inbox, the user must send a SMS message to access code. User must send ON to access code to activate the virtual box. Once the request is receive by the system, it will then validate the request. The system will check if requestor's virtual inbox is already activated. A corresponding error message will be sent to the user if his/her virtual inbox is already activated. If not activated, then the system will process the request and will activate the virtual inbox. A notification message will then be sent to the requestor.

FIG. 16C shows how to unsubscribe from a user. To unsubscribe user must send OFF + MIN of the user to unsubscribe to access code. Once the application receives the request, the system will check if the user sent the correct syntax. If the system returns invalid, the system will send the corresponding error message to user. If the system returns a valid notice / syntax, the system will check if the MIN is in proper format. IfMIN format is invalid, the system will send the corresponding error message. If the MESf is in the proper format, then the system will check if subscriber is subscribed to the user. If the subscriber is not subscribed, an error message will be sent to the request. If the subscriber has been subscribed, then the system will unsubscribe the subscriber and will send the corresponding confirmation message.

Although particular preferred embodiments have been illustrated and described herein, it will be obvious to and understood by those skilled in the art that various modifications may be made to those embodiments without departing from what is intended to be limited solely by the appended claims.

Claims

What is claimed is:

1. A system for sending Short Messaging Service ("SMS") or Multimedia Messaging Service ("MMS") messages, free of charge, by at least one prepaid mobile phone service user with no stored value credits ("sender with zero credit") to an intended recipient, comprising: a mobile phone service operator of the sender with zero credit; a mobile phone service operator of the intended recipient; a network of system-generated virtual mailboxes adapted to receive and store a plurality of SMS/MMS messages; and a messaging application that identifies, parses and stores SMS/MMS messages sent by said senders with zero credit into said virtual mailboxes, wherein said system

(a) notifies the intended recipient that there are SMS/MMS messages from a sender with zero credit in a system-generated virtual mailbox waiting to be retrieved, (b) allows the intended recipient to retrieve said SMS/MMS messages stored in a system-generated virtual mailbox, and

(c) notifies the sender with zero credit that his SMS/MMS message was retrieved by the intended recipient.

2. The system of claim 1, wherein the intended recipient can subscribe to the sender with zero credit upon retrieving the SMS/MMS message.

3. The system of claim 2, wherein after the intended recipient subscribes to the sender with zero credit, he will thereafter receive the SMS/MMS messages that the sender with zero credit sends.

4. The system of claim 1, wherein the sender with zero credit sends SMS/MMS messages to the intended recipient through the sender's mobile phone service operator via an access code.

5. The system of claim 1 , wherein the sender with zero credit and the recipient must be registered with a mobile phone service operator before they may use the mobile phone service operator services.

6. The system of claim 1, wherein the system allows the sender with zero credit to register a nickname by sending SMS instructions to his mobile phone service operator via an access code.

7. The system of claim 1, wherein the SMS/MMS messages sent by a sender with zero credit are stored in the system-generated virtual mailboxes sequentially, according to date and time.

8. The system of claim 7, wherein the SMS/MMS messages sent by a sender with zero credit and stored in the system-generated virtual mailbox are stored only for a system-defined period of time.

9. The system of claim 1 , wherein the intended recipient of an SMS/MMS message from a sender with zero credit is sent a notification free of charge that there are SMS/MMS messages in a system-generated virtual mailbox waiting to be retrieved.

10. The system of claim 9, wherein the notification sent to the intended recipient of an SMS/MMS message from a sender with zero credit contains a mobile phone identification number and a registered nickname of the sender.

11. The system of claim 1 , wherein the intended recipient of an

SMS/MMS message from a sender with zero credit is charged a fee for retrieving said SMS/MMS message from a system-generated virtual mailbox.

12. The system of claim 1 , wherein the intended recipient of an SMS/MMS message from a sender with zero credit retrieves said SMS/MMS message by sending SMS instructions to his mobile phone service operator via an access code.

13. The system of claim 1, wherein the intended recipient can retrieve at least one of said SMS/MMS messages from senders with zero credit from a system- generated virtual mailbox at any one time.

14. The system of claim 1 , wherein the intended recipient can block and unblock notifications from his mobile phone service operator that there are SMS/MMS messages from senders with zero credit in his system-generated virtual mailbox waiting to be retrieved.

15. The system of claim 1 , wherein the sender with zero credit sends

SMS/MMS messages to the intended recipient through his mobile phone service operator via an access code, and further wherein the mobile phone service operator of the intended recipient can be a different service operator from the sender's phone service operator, and further wherein the recipient's phone service operator can be in a different country from the country of the originating message.

16. The system of claim 15, wherein the system parses a mobile identification number of the sender and a mobile identification number of the intended recipient to identify where the message originated from and to where the message will be delivered.

17. The system of claim 16, wherein the intended recipient of the message from a mobile phone service operator is in a different country from the country of the originating message and is charged a higher rate.

18. The system of claim 15, wherein the system adds a MIN of the sender to a subscription table of the intended recipient, and wherein the system creates a unique entry on said subscription table.

19. The system of claim 18, wherein the unique entry will be tagged with a unique number to serve as an identification.

20. The system of claim 19, wherein the intended recipient can use the identification as a reference if the intended recipient wishes to subscribe to the sender.