Systems and methods for transmitting subject line messages

A system and method of sending subject line messages is provided. A particular method includes receiving a call setup signaling message. The call setup signaling message includes a message identifier. The method further includes determining a subject line message associated with the message identifier of the call setup signaling message. The message identifier is replaced with the subject line message. The method further includes transmitting the call setup signaling message to a called party.

FIELD OF THE DISCLOSURE

The present disclosure is generally related to systems and methods for transmitting subject line messages.

BACKGROUND

Currently, when a person receives a call, the called party may receive caller identification information (caller ID information, such as caller name or telephone number) of the call originator. For people who are busy or receive many calls, this may not be enough information to decide whether to answer the call or not.

DETAILED DESCRIPTION OF THE DRAWINGS

A system and method of sending subject line messages is disclosed. In a particular embodiment, a method includes receiving a call setup signaling message. The call setup signaling message includes a message identifier. The method further includes determining a subject line message associated with the message identifier of the call setup signaling message. The message identifier of the call setup signaling message is replaced with the subject line message. The method further includes transmitting the call setup signaling message to a called party.

In another particular embodiment, a communication system includes a processor and a memory coupled to the processor. The communication system further includes a call setup interface adapted to receive a call setup signaling message from a caller device. The call setup signaling message includes a message identifier. The communication system further includes logic to determine a subject line message associated with the message identifier. The message identifier of the call setup signaling message is replaced with the subject line message. The communication system further includes logic to transmit the call setup signaling message to a called party device via the call setup interface.

In another particular embodiment, a computer-readable medium includes operational instructions that, when executed by a processor, cause the processor to receive a call setup signaling message from a caller device. The call setup signaling message includes a Session Initiation Protocol (SIP) INVITE message. The received SIP INVITE message includes a SIP subject header that includes a message identifier. The computer-readable medium further includes operational instructions that, when executed by the processor, cause the processor to determine a subject line message associated with the message identifier based on a predetermined list. The predetermined list includes a plurality of subject line messages, where each subject line message is associated with a particular message identifier. The message identifier of the call setup signaling message is replaced with the subject line message. The computer-readable medium further includes operational instructions that, when executed by the processor, cause the processor to transmit the call setup signaling message to a called party device. Transmitting the call setup signaling message to the called party device includes transmitting the SIP INVITE message to the called party device. The transmitted SIP INVITE message includes a modified SIP subject header that includes the subject line message.

Referring toFIG. 1, a flow chart of a first particular embodiment of a method of transmitting a subject line message to a called party is illustrated, at100. The method includes, at102, receiving a call setup signaling message104. The call setup signaling message104includes a message identifier106. In a particular embodiment, the message identifier106corresponds to a pre-stored subject matter identifier that may be input or selected by a user of a customer premises equipment (CPE) device. In a particular embodiment, the CPE device may be a mobile telephone, a cellular telephone, a conventional telephone, a personal computer, a Voice over Internet Protocol (VoIP) telephone, or another end-user telephony device. The method further includes determining a subject line message that is associated with the message identifier106, as shown at108. In a particular embodiment, the message identifier106is a numerical or alpha-numerical identifier that may be linked to a subject line message114. In one embodiment, the message identifier106is linked to the subject line message114at a subject line message repository. The subject line message114may be retrieved from the subject line message repository based on the message identifier106. The message identifier106is replaced with the subject line message114, at109. The method further includes, at110, transmitting the call setup signaling message104including the subject line message114to a called party. In a particular embodiment, the called party is a destination party that receives a telephone call or other data communication from an originating party (e.g., a caller). In a particular embodiment, the subject line message114includes information provided by the caller to the called party related to a reason for a telephone call.

Referring toFIG. 2, a flow chart of a second particular embodiment of a method of transmitting a subject line message to a called party is illustrated, at200. The method includes, at202, receiving a call setup signaling message204. The call setup signaling message204includes a message identifier206. The method further includes determining a subject line message associated with the message identifier206, at208. The subject line message may be mapped or otherwise linked to the message identifier206, as shown at212. In a particular embodiment, a predetermined list210includes mapping information that maps the message identifier206to the subject line message.

In the particular embodiment illustrated inFIG. 2, the method further includes determining whether the caller is authorized to send the subject line message, at214. For example, a list of subscribers216(e.g., callers that have subscribed to a subject line message service) may be consulted to determine whether the caller is authorized to send the subject line message. As a further example, the method may include determining whether the caller is delinquent on an account (e.g., whether the caller has paid one or more recent bills). When the caller is not authorized to send the subject line message, the method ends at232since subject line message communications are not authorized for the caller.

When the caller is authorized to send the subject line message, as determined at214, the method continues at218. At218, a determination is made whether the called party is authorized to receive the subject line message. For example, a list of subscribers220(e.g., called parties that have subscribed to the subject line message service) may be consulted to determine whether the called party is authorized to receive the subject line message. As a further example, the method may include determining whether the called party is delinquent on an account (e.g., whether the called party has paid one or more recent bills). When the called party is not authorized to receive the subject line message, the method ends at232since subject line message communications are not authorized for the called party.

In the particular embodiment illustrated inFIG. 2, the method further includes determining whether the caller is allowed to send subject line messages to the called party, at222. Determining whether the caller is allowed to send subject line messages to the called party may include determining whether a telephone number of the caller is included in a list of authorized caller telephone numbers224. In a particular embodiment, the list of authorized caller telephone numbers224is a configurable list of callers that the called party can receive subject line messages from. For example, the called party may want only team members or a supervisor to be able to send subject line messages (e.g., a caller white list), while other callers are not allowed to send subject line messages (e.g., a caller black list). Thus, the caller white list may be stored to allow transmission of subject line messages from authorized callers, and the caller black list may also be stored to block transmission of subject line messages from unauthorized callers. In this manner, the receiving party (e.g., the called party) can provide for further security and filters with respect to subject line message communications. When the caller is not allowed to send subject line messages to the called party, the method ends at232.

When the caller is allowed to send subject line messages to the called party, as determined at222, the method continues at226. At226, the method includes transmitting the call setup signaling message204to the called party. The call setup signaling message204includes the subject line message.

In the particular embodiment shown inFIG. 2, the call setup signaling message204includes a subject line message that includes information230provided by a caller related to a reason for a telephone call. In a particular embodiment, the information230may be provided by a caller using various input capabilities of an end-user communication device. For example, the end-user communication device may include a “smart phone”, a cellular phone, a set-top box, or another electronic device accessible to an IP communication network. Thus, a caller may use a variety of different devices accessible to the IP communication network to provide the information230related to the reason for a particular telephone call. The reason provided by the caller may be a pre-determined message or may be a user defined custom message. Once the information230is provided by the caller via the end-user communication device, the information230may be communicated via the IP communication network to the called party, thereby facilitating enhanced information for the called party to improve end-to-end communications.

Referring toFIG. 3, a flow chart of a third particular embodiment of a method of transmitting a subject line message to a called party is illustrated, at300. At302, a call setup signaling message304is received from a caller device340via an IP Access network312. In a particular embodiment, the call setup signaling message304includes a Session Initiation Protocol (SIP) INVITE message306. The received SIP INVITE message306includes a SIP subject header308which includes a message identifier310.

In a particular embodiment, the SIP INVITE message306is received at an originating IP Multimedia Subsystem (IMS) session call session control functions (S-CSCF) server. The originating IMS S-CSCF server sends the telephone call to a particular subject line messaging application server. The particular subject line messaging application server is selected based on originating initial filter criteria (iFC) retrieved for the caller device from a home subscriber server (HSS) at registration. In a particular embodiment, the originating IMS S-CSCF sends the telephone call to an application server assigned to the caller. The application server assigned to the caller performs originating feature treatment, such as determining if the caller subscribes to the subject line message service. If the caller does not subscribe to the subject line message service, the subject line messaging application server removes the SIP subject header308. If the caller subscribes to the subject line message service, the SIP subject header308is not removed. In a particular embodiment, the originating IMS S-CSCF server queries the HSS to determine a terminating IMS S-CSCF associated with the called party. The originating IMS S-CSCF server sends the telephone call to the terminating IMS S-CSCF associated with the called party. Based on terminating iFC, the terminating IMS S-CSCF determines if the called party subscribes to the subject line message service. If the called party does not subscribe to the subject line message service, the telephone call is routed to another application server, based on the terminating iFC. If the called party subscribes to the subject line message service, the telephone call is routed to the subject line messaging application server.

In a particular embodiment, the subject line messaging application server determines if the called party has enabled the subject line message service. If the called party has not enabled the subject line message service or has disabled the subject message service, the subject line messaging application server removes the SIP subject header308. In another particular embodiment, the subject line messaging application server determines whether the caller is allowed to send subject line messages to the called party. For example, determining whether the caller is allowed to send subject line messages to the called party may include determining whether a telephone number of the caller is included in a list of authorized caller telephone numbers. If the caller is not on the list of authorized caller telephone numbers, the subject line messaging application server removes the first SIP subject header308. If the caller is on the list of authorized caller telephone numbers, the method proceeds to314.

At314, a subject line message334associated with the message identifier310is determined, and the message identifier310is replaced with the subject line message334. In a particular embodiment, the subject line message334is determined by accessing information from a subject line message repository316. The subject line message repository316may be stored within a database accessible to a network service provider via an IP communication network. In one embodiment, the method includes retrieving the subject line message334from the subject line message repository316based on the message identifier310of the received SIP INVITE message306. The subject line message repository316may include a plurality of subject line messages, where each subject line message is associated with a particular message identifier. For example, inFIG. 3, a first message identifier318is associated with a first subject line message320, and a second message identifier322is associated with a second subject line message324. It should be understood that the subject line message repository316may include any number of message identifers, and each message identifier may be associated with a particular subject line message stored in a retrievable format.

At326, the call setup signaling message304is transmitted via the IP Access network312to a called party device342. The call setup signaling message304includes the SIP INVITE message306, including a modified SIP subject header332. The modified SIP subject header332includes the subject line message334to be delivered to the called party device342.

In a particular embodiment, the functions illustrated in boxes302,314,316and326are elements of a Session and Application Layer of a Third Generation Partnership Program (3GPP) IMS architecture. The 3GPP IMS architecture may include a plurality of different interconnected communication elements that may be used for data and call traffic communications. The 3GPP IMS architecture is an example of a next generation network (NGN). For example, the NGN may be based on an Alliance for Telecommunications Industry Solutions (ATIS) NGN framework, a European Telecommunications Standards Institute (ETSI) NGN framework, or a Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN) NGN framework. Next generation networks use Session Initiation Protocol (SIP) for call setup signaling. An NGN architecture separates network accesses, session control, and application services to allow rapid deployment of new application services. An NGN architecture is capable of providing a large variety of real-time multimedia communication services consistently on various network accesses. Request for Comment (RFC) 3261 (SIP) supports a header subject to enable a subject text to be sent from the caller to the called party.

Thus, call setup signaling messages may be used within an IMS context to facilitate communication of message identifiers linked to specific subject line messages as shown. Use of NGN technologies can enhance network operator performance and reduce cost as well as provide increased functionality. In addition, the subject line message capabilities disclosed provide a new feature for an NGN operator to differentiate from more basic services such as caller ID information (e.g. caller name or telephone number). Having the capability for the called party to determine who is calling and the reason for the call may enable the called party to make better decisions when determining whether to answer an incoming call and may allow the called party to differentiate calls having a higher priority or urgent nature as compared to other calls which may be suitable for a later call back.

The disclosed subject line messaging systems and methods provide enhanced communication and additional information with respect to called parties receiving communications, such as telephone calls from originating calling parties. In a particular embodiment, the disclosed subject line messaging systems and methods may be implemented using a subject line messaging service that is enabled using an IMS network based platform and configured using an originating iFC and a terminating iFC based on subscriber service profiles stored within an HSS system. As another benefit, use of the SIP messages and signaling mechanisms of the disclosed subject matter provides for more ubiquitous implementations with respect to service providers having a need to balance user acceptance against service manageability and network performance.

Referring toFIG. 4, a block diagram of a particular embodiment of a communication system is illustrated, at400. The communication system400includes a subject line messaging application server401, a web server435, a device management server441, a SIP proxy server414, a home subscriber server (HSS)424, and an IP Access Network428. The subject line messaging application server401is coupled to the SIP proxy server414, which is coupled to the HSS424. In addition, the subject line messaging application server401is coupled to the web server435, which is coupled to the device management server441.

In the embodiment shown inFIG. 4, the IP Access Network428is in communication with a plurality of different end-user communication devices (e.g., caller devices and called party devices). For example, the end-user communication devices may include a wireless device426(e.g., a wireless telephone or cellular telephone), a hand-held computing device451(e.g., a personal digital assistant (PDA) or a tablet computer), a laptop computer452, a desktop computer453, or a VoIP telephone454, among other alternatives. The IP Access network428may receive communications from any device that is connected to an IP network.

The subject line messaging application server401includes a processor402, a memory404coupled to the processor402, subject line messaging application server logic406, and a call setup interface412. In a particular embodiment, the subject line messaging application server logic406is implemented by software stored within the memory404. In another embodiment, the subject line messaging application server logic406may be implemented by hardware or programmable logic circuitry.

The web server435includes a subject line message repository436, a web portal interface432, and web server logic434. In a particular embodiment, the web server logic434may be implemented in hardware, software, firmware or any combination thereof.

The device management server441includes a caller device interface440and device management server logic442. In a particular embodiment, the device management server logic442may be implemented in hardware, software, firmware or any combination thereof.

During operation, a user may communicate with and receive access to the web server435via messages utilizing the IP Access Network428. In a particular embodiment, a message received at the IP Access Network428is then communicated to the web server435. For example, the user may access the web server435via the web portal interface432to provide a user selected subject line message430. The user selected subject line message430is provided by the user of a caller device to request a particular subject line message to be stored at the caller device for subsequent use during communication. In one embodiment, the user selected subject line message430includes a default subject line message selected from a list of default subject line messages displayed via the web portal interface432. In another embodiment, the user selected subject line message430includes a user defined subject line message (e.g., a custom message) supplied by the user via the web portal interface432. The user selected subject line message430is received at the web portal interface432and is processed by the web server logic434. Further, the web portal interface432is adapted to receive a user selection of at least one caller device to receive the user selected subject line message430. For example, the caller device may include the wireless device426, the hand-held computing device451, the laptop computer452, the desktop computer453, or the VoIP telephone454, among other alternatives. The web server logic434determines a message identifier418of the user selected subject line message430and determines at least one unique identifier (UID)438associated with the at least one caller device selected by the user to receive the user selected subject line message430. For example, the user may select more than one caller device to receive the user selected subject line message430, resulting in more than one UID438being associated with a particular user selected subject line message430and message identifier418. The web server logic434stores the user selected subject line message430, the message identifier418, and the at least one UID438at the subject line message repository436.

In a particular embodiment, the subject line message repository436is further adapted to store a plurality of default subject line messages. In one embodiment, the default subject line messages include information related to a reason for a telephone call (e.g., health issue, question, weekend plans, advice). Further, the reason for the telephone call may include the nature of the telephone call (e.g., an urgency of the telephone call). Providing the reason for the telephone call via the subject line message may enable called parties to decide whether to answer an incoming telephone call or to reject the incoming telephone call. Caller ID information may not be available at times (e.g., a PBX number), and even if Caller ID information is available it provides no information about the reason for the telephone call or the urgency of the telephone call. The web portal interface432is further adapted to display one or more of the plurality of default subject line messages for user selection. Alternatively, the web portal interface432may receive a user defined subject line message. For example, the user defined subject line message allows a user to provide a non-generic message not displayed in the list of default subject line messages. Thus, the user of an end-user communication device (e.g., the wireless device426) may select a default subject line message or may provide a custom subject line message.

In a particular embodiment, the user defined subject line message may be screened to determine whether the message includes allowable subject matter. In one embodiment, the web server logic434includes logic to determine whether the user defined subject line message includes allowable subject matter, which may include logic to identify offensive subject matter contained in the user defined subject line message. For example, user defined subject line messages may be screened for allowable subject matter based on parental control settings or other information associated with a particular subscriber account. In this manner, the web server logic434may remove or otherwise restrict subject matter deemed offensive to a particular user or owner of a particular end-user communication device. In one embodiment, the web server logic434includes logic to store the user defined subject line message when the user defined subject line message includes allowable subject matter. Subject matter that is deemed allowable based on the web server filtering process is stored within the subject line message repository436. In one embodiment, the web server logic434includes logic to reject the user defined subject line message when the user defined subject line message does not include allowable subject matter. Subject matter that is not deemed allowable based on the web server filtering process is rejected and not stored within the subject line message repository436.

In a particular embodiment, the web portal interface432is adapted to allow the user to enable or disable subject line message services. In another particular embodiment, the web portal interface432is adapted to receive a user selection of one or more telephone numbers of callers that are authorized to send subject line messages, and the web server logic434includes logic to store the one or more authorized telephone numbers at the subject line message repository436as a list of enabled telephone numbers. In another particular embodiment, the web portal interface432is adapted to receive a user selection of one or more telephone numbers of callers that are not authorized to send subject line messages, and the web server logic434includes logic to store the one or more unauthorized telephone numbers at the subject line message repository436as a list of disabled telephone numbers. For example, the called party may want only team members or a supervisor to be able to send subject line messages (e.g., a caller white list), while other callers are not allowed to send subject line messages (e.g., a caller black list). Thus, the caller white list may be stored to allow transmission of subject line messages from authorized callers, and the caller black list may also be stored to block transmission of subject line messages from unauthorized callers. In this manner, the receiving party (e.g., the called party) can provide for further security and filters with respect to subject line message communications.

After storage at the subject line message repository436, information444including the user selected subject line message430, the message identifier418and the at least one UID438is sent from the subject line message repository436to the device management server logic442of the device management server441. The caller device interface440of the device management server441receives the information444from the device management server logic442and transmits the information444through the IP Access Network428for storage at one or more of the end-user communication devices. For example, the one or more end-user communication devices may include the wireless device426, the hand-held computing device451, the laptop computer452, the desktop computer453, or the VoIP telephone454, among other alternatives. The information444includes a particular UID438associated with a particular end-user communication device. As noted above, in the event that the user selects more than one end-user communication device to receive the user selected subject line message430, each selected end-user communication device receives a different UID438(e.g. a first UID associated with wireless device426, and a second UID associated with VoIP telephone454).

After receipt of the information444from the device management server441, the end-user communication device (e.g., a caller device such as the wireless device426) may store the information444including the user selected subject line message430, the message identifier418, and the UID438associated with the particular device in memory. As previously described, the message identifier418is used to retrieve the user selected subject line message430from the subject line message repository436. Thus, storing the message identifier418at the end-user communication device prevents a user from editing or modifying the user selected subject line message430in order to send a subject line message containing offensive subject matter. Further, the UID438may be used to ensure that subject line messages are sent from authorized end-user communication devices, as described below.

A caller may select the user selected subject line message430at a caller device for transmission to a called party device, allowing the caller to provide information to a called party related to a reason for a telephone call. In one embodiment, the caller selects the user selected subject line message430via a keypad, touchscreen, or other input at the caller device. For example, a caller at the wireless device426may want to provide a reason for the telephone call to the called party at the VoIP telephone454. A call setup signaling message416including the message identifier418is communicated from the wireless device426to the SIP proxy server414. The message identifier418is then communicated via the call setup interface412of the subject line messaging application server401. The subject line messaging application server logic406retrieves a subject line message422associated with the message identifier418from the subject line message repository436of the web server435. The subject line messaging application server logic406communicates the subject line message422via the call setup interface412to the SIP proxy server414. The call setup signaling message416including the subject line message422is communicated from the SIP proxy server414via the IP Access Network428to the called party device (e.g., the VoIP telephone454). Thus, in a particular embodiment, the message identifier418of the call setup signaling message416received from the caller device (e.g., the wireless device426) is translated into the subject line message422for delivery via the IP Access Network428to the called party device (e.g., the VoIP telephone454).

The home subscriber server (HSS)424is adapted to provide IP based authorization, accounting and authentication (AAA) functions and is adapted to store one or more subscriber profiles, registration data, network policy rules, or any combination thereof. The SIP proxy server414also includes logic to retrieve data from the HSS424. In one embodiment, the SIP proxy server414retrieves data from the HSS424based on a particular subscriber phone number associated with a particular end-user communication device.

In addition, the SIP proxy server414includes IP Multimedia Subsystem (IMS) session call session control functions (S-CSCF). In one embodiment, the SIP proxy server414includes originating S-CSCF and terminating S-CSCF. In a particular embodiment, the originating S-CSCF retrieves an originating initial filter criteria (iFC) from the HSS424, and the terminating S-CSCF retrieves a terminating iFC from the HSS424. In one embodiment, the originating iFC and the terminating iFC are used by the SIP proxy server414to route the telephone call to the subject line messaging application server401, which manages the subject line message services of caller devices and called party devices.

The subject line messaging application server401may be used to prevent subject line messages being sent from a particular caller device. For example, the particular caller device may be associated with a subscriber that has disabled the subject line message service. As a further example, the caller may be delinquent on an account (e.g., the caller has not paid one or more recent bills). In the event that the subscriber associated with the particular caller device (e.g., the caller device340ofFIG. 3) has disabled the service, a SIP subject header (e.g., the SIP subject header308ofFIG. 3) including the message identifier (e.g., the message identifier310ofFIG. 3) is removed from a SIP INVITE message (e.g., the SIP INVITE message306ofFIG. 3). Otherwise, the subject line message (e.g., the subject line message334ofFIG. 3) is retrieved from the subject line message repository (e.g., the subject line message repository316ofFIG. 3) based on the message identifier.

The subject line messaging application server401may also be used to prevent subject line messages being sent to a particular called party device. For example, the particular called party device may be associated with a subscriber that has disabled the subject line message service. As a further example, the called party may be delinquent on an account (e.g., the called party has not paid one or more recent bills). In the event that the subscriber associated with the particular called party device (e.g., the called party device342ofFIG. 3) has disabled the service, a modified SIP subject header (e.g., the modified SIP subject header332ofFIG. 3) including the subject line message (e.g., the subject line message334ofFIG. 3) is removed from the SIP INVITE message (e.g., the SIP INVITE message306ofFIG. 3). As a further example, the subscriber associated with a particular called party device may have created a white list or a black list. If a particular caller device (e.g., the caller device340ofFIG. 3) is included in the white list, the modified SIP subject header including the subject line message is transmitted to the particular called party device. If the particular caller device is included in the black list, the modified SIP subject header including the subject line message is removed from the SIP INVITE message. In one embodiment, the SIP proxy server414retrieves information related to the white list and the black list from the HSS424based on the UID of the particular caller device.

Referring toFIG. 5, a first particular embodiment of a web portal interface is illustrated, at500. In a particular embodiment, the web portal interface432as shown inFIG. 4may be implemented as the web portal interface500as shown inFIG. 5. Referring toFIG. 5, in a particular embodiment, the web portal interface500includes an area503for a user to select a default subject line message from a list of predetermined subject line messages. For example, a default subject line message may include the text “Urgent—Health Issue”504, “Urgent—Question”506, “Not Urgent—Weekend Plans”508, “Not Urgent—Advice”510, among other alternatives. A user may select one or more of the default subject line messages using a checkbox511or other selection means. In the embodiment shown inFIG. 5, the web portal interface500includes an area513for the user to enter a user defined subject line message. For example, the user may enter user defined subject line message text into a text box514. Upon entering the user defined subject line message text at the text box514, the user may click a submit button516to submit the user defined subject line message. In one embodiment, after clicking the submit button516to submit the user defined subject line message, the system determines whether the user defined subject line message includes allowable subject matter. In the embodiment shown inFIG. 5, the web portal interface500includes an area515for the user to select one or more caller devices to receive one or more subject line messages. For example, the one or more caller devices may include the VoIP telephone518, the desktop computer520, the laptop computer522, or the wireless telephone524, among other alternatives. The user may request that the one or more user selected subject line messages be transmitted to the selected caller devices by clicking a download button526. For example, the one or more subject line messages may be transmitted to the one or more caller devices via the caller device interface440of the device management server411, as shown inFIG. 4.

Referring toFIG. 6, a second particular embodiment of a web portal interface is illustrated, at600. When a user enters a user defined subject line message604at the text box514, the system determines whether the user defined subject line message604contains allowable subject matter. For example, in the particular embodiment shown inFIG. 6, the user defined subject line message604includes the message “ANSWER YOUR PHONE #$%@#.” Because the user defined subject line message604contains offensive subject matter, a message606may be displayed. For example, the message606may include the message, “The Message You Entered Contains Offensive Subject Matter. Please Enter a New Message”. A user may then enter a new user defined subject line message604at the text box514. In the event that the user defined subject line message604includes allowable subject matter, the user defined subject line message604is stored at a subject line message repository, such as the subject line message repository436ofFIG. 4. Thus, the system includes a filtering process that automatically filters user defined subject line messages for suspicious or abusive language. In one embodiment, suspicious or abusive language may be flagged for administrator review or approval.

Referring toFIG. 7, a third particular embodiment of a web portal interface is illustrated, at700. The web portal interface700includes an area702to enable or disable a subject line message service. For example, a user may click an enable button704to enable the subject line message service. Alternatively, the user may click a disable button706to disable the subject line message service.

In one embodiment, the web portal interface700includes an area708to receive a user selection of one or more telephone numbers from which subject line messages may be received. For example, the user may enter one or more authorized telephone numbers into a text box710. Upon entering the one or more authorized telephone numbers at the text box710, the user may click a submit button712to submit the authorized telephone numbers. In one embodiment, the one or more authorized telephone numbers are stored as a list of enabled telephone numbers at a subject line message repository, such as the subject line message repository436ofFIG. 4.

In another embodiment, the web portal interface700includes an area714to receive a user selection of one or more telephone numbers from which subject line messages may not be received. For example, the user may enter one or more unauthorized telephone numbers into a text box716. Upon entering the one or more unauthorized telephone numbers at the text box716, the user may click a submit button718to submit the unauthorized telephone numbers. In one embodiment, the one or more unauthorized telephone numbers are stored as a list of disabled telephone numbers at the subject line message repository, such as the subject line message repository436ofFIG. 4.

Referring toFIG. 8, an illustrative embodiment of a general computer system is shown and is designated800. The computer system800can include a set of instructions that can be executed to cause the computer system800to perform any one or more of the methods or computer based functions disclosed herein. The computer system800may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices. For example, the general computer system800may include or be included within any one or more of the end-user communication devices (e.g. caller devices and called party devices), servers, repositories, and network equipment illustrated inFIG. 3andFIG. 4.

As illustrated inFIG. 8, the computer system800may include a processor802, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both. Moreover, the computer system800can include a main memory804and a static memory806, that can communicate with each other via a bus808. As shown, the computer system800may further include a video display unit810, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, or a cathode ray tube (CRT). Additionally, the computer system800may include an input device812, such as a keyboard, and a cursor control device814, such as a mouse. The computer system800can also include a disk drive unit816, a signal generation device818, such as a speaker or remote control, and a network interface device820.

In a particular embodiment, as depicted inFIG. 8, the disk drive unit816may include a computer-readable medium822in which one or more sets of instructions824, e.g. software, can be embedded. Further, the instructions824may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions824may reside completely, or at least partially, within the main memory804, the static memory806, and/or within the processor802during execution by the computer system800. The main memory804and the processor802also may include computer-readable media.

The present disclosure contemplates a non-transitory computer-readable medium that includes instructions824or receives and executes instructions824responsive to a propagated signal, so that a device connected to a network826can communicate voice, video or data over the network826. Further, the instructions824may be transmitted or received over the network826via the network interface device820.

A next generation network (NGN) that includes 3GPP IMS standards has been illustrated. The NGN system uses a SIP Protocol for call setup signaling. The NGN architecture separates network accesses, such as control and application services to allow rapid deployment of new application services and features. The NGN network is capable of providing a large variety of real time multimedia communication services consistently over various network access interfaces. Accordingly, the disclosed system provides a framework that enable callers to send subject line messages along with call setup signaling messages to inform the called party about the nature of the call before the call is answered. The disclosed framework enhances user end-point device capabilities for sending and receiving and displaying by introducing a new application server to store messages and also to insert the subject line messages in the call offered to the called party device. The disclosed system and method is based on SIP standards to provide inter-operability in a particular embodiment. The subject line message service provides an enhanced service provider web portal to allow users to create and store messages to be sent at call setup time. The system also allows a user to enable or disable the service by callers and called parties and enables filtering of subject line messages for allowable subject matter. The system further includes a scan process that automatically filters newly created messages for suspicious or abusive language and flags such language for administrator review and approval. In addition, the system includes a method to propagate approved messages including subject line information to a variety of different customer premises equipment (CPE) devices owned by the message creator. In addition, the system and method allows a user to set-up an authorize a list of people that can send and receive the subject line messages as defined.