Communication with customers is an important part of customer management. The customer communication may occur via email, standard mail or by way of telephone calls. Such customer communications may have varying purposes. For example, the customer communications may identify new products or services available for purchase, provide information related to changes in an existing product or service, and the like. In all of the above cases, customers may be contacted without advance notice. Such con- tact without advance notice may be bothersome or inconvenient to the customers.

Mobile devices, such as, for example, cellular telephones, have increasingly become a common consumer electronic item used by a significant number of people. Certain functionalities associated with such mobile devices may enable network providers and the like to contact users of the devices without annoying or inconveniencing those users.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanying figures. In the figures, the left- most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference number in different instances in the description and the figures may indicate similar or identical items.

FIG. 1 illustrates an exemplary system in which exemplary implementations may be implemented.

FIG. 2 illustrates one example of at least a portion of the system, implemented using a cellular or wireless network. FIG. 3 illustrates the mobile device consistent with an exemplary embodiment. FIG. 4 illustrates server consistent with an exemplary embodiment. FIG. 5 illustrates an exemplary information conveyance procedure. DETAILED DESCRIPTION

The following description describes implementations related to methods and apparatuses for contacting users of wireless or otherwise mobile devices, and conveying information thereto, in a manner that eliminates or mitigates inconveniencing the users if they do not wish to be contacted. In one implementation, a message is sent to a wireless device. The message may include a link, contact phone number, universal resource locator (URL) ₁ or the like. Furthermore, the message may include a short description of the goods and/or services being offered. In a particular implementation, the link, contact phone number, URL, or the like, may be used by the user to contact an entity (e.g., wireless services network provider) that generated the message or conveyed the message. On the entity side, a voice mailbox (e.g., a service mailbox) may be available to the users that contact the entity in response to receiving the message. The voice mailbox may include further information, in prerecorded and/or live voice format, that further describes the goods and/or services being offered. In another particular im- plementation, the message is conveyed to a mobile device by way of a short messaging service (SMS) message, an email message or a multimedia messaging service (MMS) message.

FIG. 1 illustrates an exemplary system 100 in which exemplary implementations may be implemented. System 100 may include multiple mobile stations 102 through 106 (collectively referred to herein as "mobile stations 102") connected with a server 108 via a network 110 using wired or wireless links. The server 108 may be a single server or a plurality of servers, where the plurality of servers may be located in a number of different geographical locations. The network 110 may include one or more networks of any type, including a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network, such as the Public Switched Telephone Network (PSTN) or a Public Land Mobile Network (PLMN), an intranet, the Internet or a combination of networks. The PLMN(s) may further include a packet-switched sub-network, such as, for example, General Packet Radio Service (GPRS). Mobile stations 102 through 106 may include a telephone, cellular telephone, Personal Communications System (PCS) terminal, or the like. A PCS terminal may combine a cellular telephone with data processing, facsimile and data communications capabilities. Mobile stations 102 through 106 may further include a personal digital assistant (PDA), a conventional laptop and/or palmtop receiver, or another device that includes a transceiver, or the like. A PDA may include a telephone, a pager, Internet/intranet access, a web browser, an organizer, calendars and/or a global positioning system (GPS) receiver. One or more of mobile stations 102 may further be referred to as a "pervasive computing" device.

FIG. 2 illustrates one example of at least a portion of the system 100, implemented using a cellular or wireless network. The system 100 may include a mobile device 200 and a mobile device 202. The system 100 may include one or more base station controllers (BSCs) 204 and 206, multiple base stations (BSs) 208 - 218 that include multiple base station antenna arrays, and one or more mobile switching centers (MSCs) 220. The system may also include a gateway (not illustrated) coupled to the MSC 220. The system 100 may include components usable for transmitting data to and from mobile devices 200 and 202. Such components may include the base station antenna arrays, which transmit and receive, via appropriate data channels, data from mobile devices within their vicinity. Base stations 208 - 218 connect to their respective antenna arrays, and format the data transmitted to, or received from the antenna arrays in accordance with existing techniques, for communicating with the BSCs 204 and 206, or a mobile device, such as mobile devices 200 and 202. Among other functions, BSCs 204 and 206 may route received data to either the MSC 220 or a base station (e.g., BSs 208 - 218). The MSC 220 routes received data to BSC 204 or 206. The gateway may route data received from an external domain (not illustrated) to an appropriate MSC (such as MSC 220), or from an MSC to an appropriate external domain. The server 110 (not shown in FIG. 2) may connect to the network 110 via the MSC 220 or via another network (e.g., the Internet) connected to the gateway.

FIG. 3 illustrates the mobile device 102 consistent with an exemplary embodiment. The mobile device 102 may include a transceiver 300, an antenna, an equalizer 302, an optional encoder/decoder 304, a processing unit 306, a memory 308, an output device(s) 310, an input device(s) 312, and a bus 314.

Transceiver 300 may include transceiver circuitry for transmitting and/or receiving symbol sequences in a network, such as network 100, via the antenna. The transceiver 300 may include, for example, a conventional RAKE receiver. The transceiver 300 may further include mechanisms for estimating the signal- to-interference ratio (SIR) of received symbol sequences. The transceiver 300 may additionally include mechanisms for estimating the propagation channel frequency.

The equalizer 302 may store and implement trellises for estimating received symbol sequences using, for example, a maximum likelihood sequence estimation technique. The equalizer 302 may additionally include mechanisms for performing channel estimation. The encoder/decoder 304 may include circuitry for decoding and/or encoding received or transmitted symbol sequences.

The Baseband processing unit 306 may perform data processing functions for inputting, outputting, and processing of data including data buffering and device control functions, such as call processing control, user interface control, and the like. The processing unit 306 may include a processor, microprocessor, or processing logic that may interpret and execute instructions. The memory 308 may provide permanent, semi-permanent, or temporary working storage of data and instructions for use by the processing unit 306 in performing processing functions. The memory 308 may include large-capacity storage de- vices, such as a magnetic and/or optical recording medium and its corresponding drive.

The output device(s) 310 may include mechanisms for outputting data in video, audio, and/or hard copy format. The input device(s) 312 permit entry of data into the mobile device 102 and may include a user interface and a microphone (not shown). The microphone can include mechanisms for converting audi- tory input into electrical signals. The bus 314 interconnects the various components of mobile device 102 to permit the components to communicate with one another. The configuration of components of mobile station 102 illustrated in FIG. 3 is for illustrative purposes only. One skilled in the art will recognize that other configurations may be implemented. FIG. 4 illustrates server 108 consistent with an exemplary embodiment. Server 108 may include a processing unit 400, a memory 402, an input device(s) 404, an output device(s) 406, a network interface(s) 408 and a bus 401.

The processing unit 400 may perform all data processing functions for inputting, outputting, and proc- essing of data. The processing unit 400 may include a processor, microprocessor, or processing logic that may interpret and execute instructions. The memory 402 may provide permanent, semi-permanent, or temporary working storage of data and instructions for use by the processing unit 400 in performing processing functions. The memory 402 may include large-capacity storage devices, such as a magnetic and/or optical recording medium and its corresponding drive. The input device 404 may include a mechanism that permits an operator to provide information to the server 108, such as a keyboard, a mouse, a pen, voice recognition and/or biometric mechanisms, etc. The output device 406 may include a mechanism that outputs information to the operator, including a display, a printer, a speaker, etc. The network interface 408 may include a mechanism that enables server 108 to communicate with other devices and/or systems. For example, the network interface 408 may include mechanisms for communicating with another device or system via a network, such as network 110. The bus 410 may interconnect the various components of the server 108 to permit the components to communicate with one another.

The server 108, consistent with exemplary implementations, may perform certain processes, as will be described in detail below. The server 108 may perform these processes in response to the processing unit 400 executing software instructions contained in a computer-readable medium, such as memory 402. A computer-readable medium may be defined as a physical or logical memory device and/or a carrier wave.

The software instructions may be read into the memory 402 from another computer-readable medium, or from another device via the network interface 408. The software instructions contained in the memory 402 may cause processing unit 400 to perform processes described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement processes consistent with exemplary implementations. Thus, implementations are not limited to any specific combination of hardware circuitry and software.

The configuration of components of server 108 illustrated in FIG. 4 is for illustrative purposes only. One skilled in the art will recognize that other configurations may be implemented. Furthermore, as those of skill in the art appreciate, a plurality of servers of the type illustrated in FIG. 4 may be implemented by the systems and methods described herein.

The components discussed in the forgoing, in particular the mobile devices 102, the server 108 and the network 110, are capable of generating and communicating using text messages. A text message can include a SMS message, an MMS message, an enhanced messaging service (EMS) message, or other communications that are transmitted according to a text-based messaging protocol. A text message can also include a text-based message that is transmitted to mobile devices over a Global System for Mobile communications (GSM) network, a time division multiple access (TDMA) network, a code division multiple access (CDMA) network or other network.

Specifics of exemplary procedures are described below. However, it should be understood that certain acts need not be performed in the order described, and may be modified, and/or may be omitted entirely, depending on the circumstances. Moreover, the acts described may be implemented by a computer, processor or other computing device based on instructions stored on one or more computer- readable storage media. The computer-readable storage media can be any available media that can be accessed by a computing device to implement the instructions stored thereon. The exemplary proce- dures described below may reference one or more of the exemplary devices and components described in FIGS. 1 - 4. Therefore, one or more of the devices and information illustrated in FIGS. 1 - 4 may used to implement the described procedures. However, the referenced devices are not limiting of the described procedures. FIG. 5 illustrates an exemplary information conveyance procedure. At block 502, a server, such as server 108, stores voice information that may pertain to goods and/or services. For example, such goods and/or services may include invoice information, details of changes associated with goods and/or services, offers for new or improved goods and/or services, advertisements, or the like. In one implementation, the voice information may pertain to goods and/or services that include user selectable op- tions, provided in an auditory listing of actions that may be initiated by a user, which cause the server to perform an action. The actions performable by the server may include conveying information (e.g., billing, current or accumulated data and/or voice usage, or network status) to a requesting mobile, sending a command(s) to a requesting mobile device that causes reconfiguration of one or more operating characteristics (e.g., modifying/adding ringtones, modifying voice/data speed, or adding/removing fea- tures) of the mobile device.

At block 504, the server generates a text message. The text message may be an SMS message, an MMS message, an EMS message, an email message, or the like. The text message may summarize, in text format, the voice information stored on the server. In one implementation, the text message sum- marizes or is a portion of the voice information stored in a voice mailbox associated with the server. In addition, the text message may include data, such as a telephone number, a link (e.g., a URL), or the like, that may be used by a mobile device, such as the mobile device 102, to interface with the server. In one implementation, the data associated with the text message simply instructs a customer or user viewing the message to perform an action. For example, the data may instruct the customer or user to call a phone number to access the voice information stored on the server. Alternatively, or in addition, the data may instruct the customer to use an input device (e.g., a keypad) associated with a mobile device to initiate accessing the voice information stored on the server. At block 506, the server communicates the text message to one or more mobile devices. In one implementation, the text message includes invoice information, so the text message is sent to a single mobile device, or a collection of devices that may be associated with a single user or customer. In another implementation, the text message includes information related to goods and services, advertisements, or the like, so the text message may be conveyed to a plurality of mobile devices (e.g., devices belonging to disparate users) and/or devices enabled to connect to a network, such as the network 110.

At block 508, at least one mobile device receives the text message generated at block 504. At block 510, a user of the mobile device views the text message received at block 508. At block 512, the user of the mobile device makes use the data to connect to the server. At block 514, the server determines that the mobile device has used the data to connect thereto and enables the mobile device to connect to or access the voice information stored at block 502. In one implementation, at block 514, the server is operative to receive a request to access voice information stored on the server, and to determine if the request originated from a mobile device that is authorized to access the voice information. Authorizing access to the voice information may require password verification, comparing a caller ID associated with a mobile device requesting the voice information to one or more phone numbers associated with mobile devices that were to receive the text message, confirming that a unique identification number associated with a requesting mobile device is recognized by the server, or the like. Alternatively, or in addition to the foregoing, the server may expect to receive an encryption key or encryption information from a mobile device requesting access to the voice information stored on the server. The server may use the encryption key to verify the requesting mobile device is authorized to access the voice information stored on the server.

In one implementation, the server may also enable a mobile device to connect to a customer liaison representative (i.e., a person) in addition to retrieving the voice information stored on the server. For example, the server may prompt the mobile device to enter numeric and/or alphanumeric sequences that enable the server to connect the mobile device to one or more customer liaison representatives.

At act 516, as part of a monitoring process, the server may retain information related to the mobile device that connected to or accessed the voice information stored at block 502. For example, the server may reference a list of mobile devices and information associated therewith that were communicated the text message at act 506, and cross-reference a caller ID, a unique identification number, or the like, of the mobile device to generate an accounting that the mobile device has connected or accessed the voice information. Retaining accounting information related to mobile devices that received one or more text messages and subsequently accessed associated stored voice information may be used for various purposes. For example, the server may send a reminder or resend the text message of act 506, after a period of time, to mobile devices that have not accessed the stored voice information. In addition, the retained information may be used to compile statistics associated with one or more mobile devices that have been communicated text messages. Such statistics may be used by the server to determine if certain mobile devices shall receive such text messages in the future.

For the purposes of this disclosure and the claims that follow, the terms "coupled" and "connected" may have been used to describe how various elements interface. Such described interfacing of various elements may be either direct or indirect. Although the subject matter has been described in language spe- cific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described.

Rather, the specific features and acts are disclosed as preferred forms of implementing the claims. The specific features and acts described in this disclosure and variations of these specific features and acts may be implemented separately or may be combined.