CN103339898B - For providing the method and system of enhancement mode event notice in UPnP home network environment - Google Patents

Abstract

A method and system are provided for providing incoming event notifications to a telephony control point in a UPnP home network environment. Information associated with the remote party is retrieved by the telephony server when an incoming event associated with the remote party arrives at the telephony server. Generates an incoming event notification associated with the incoming event. The incoming event notification includes information associated with the remote party. The incoming event is forwarded to at least one telephony control point in the UPnP home network environment together with the incoming event notification. When an incoming event arrives at a telephony control point, information associated with the remote party is displayed on a display of at least one telephony control point along with an incoming event notification.

Description

intended to provide in a UPnP home networking environment Method and system for enhanced event notification

technical field

The present invention relates generally to the field of Universal Plug and Play (UPnP) communications, and more particularly to providing enhanced event notification in a UPnP home network environment.

Background technique

UPnP is a set of computer network protocols promulgated by the UPnP Forum. The goal of UPnP is to allow access for seamless connectivity and to simplify network implementation (eg, data sharing, communication, and entertainment) in home and business environments. These goals are achieved by defining and publishing the UPnP device control protocol built on open, Internet-based communication standards.

The UPnP technology can meet the needs of a wide range of devices in a home network. UPnP provides discovery, control, and eventing mechanisms. The discovery mechanism is initiated using the Simple Service Discovery Protocol (SSDP) protocol. The event mechanism follows the General Event Notification Architecture (GENA) protocol. Using these techniques, UPnP makes running UPnP devices available or unavailable to other devices in the UPnP home network.

The UPnP architecture allows for peer-to-peer networking of personal computers (PCs), networked home appliances, and wireless devices. The UPnP architecture is a distributed , open architecture. The UPnP architecture supports zero-configuration networking. For example, a UPnP-compliant device from any vendor can dynamically join a network, obtain an Internet Protocol (IP) address, declare its name, communicate its capabilities upon request, and learn about the presence and capabilities of other devices. On the other hand, UPnP devices are able to leave the UPnP home network automatically without leaving any unwanted state information.

The basis of UPnP networking is Internet Protocol (IP) addressing. Each UPnP device includes a Dynamic Host Configuration Protocol (DHCP) client that searches for a DHCP server when the UPnP device connects to the UPnP network for the first time. If no DHCP server is available, the UPnP device assigns itself an address. If during a DHCP transaction, the UPnP device acquires a domain name, eg, through a Domain Name System (DNS) server or via DNS forwarding, the UPnP device uses that name in subsequent network operations; otherwise the UPnP device uses its IP address.

The UPnP forum also provides telephony services for extending the user's experience in accessing telephony services in the home, such as messaging services, presence services, and call handling (Packet Switched (PS)/Circuit Switched (CS) calls )Serve. Similar to the UPnP Device Architecture (DA), Telephony defines three categories of devices, namely, Telephony Servers (TS) that provide messaging and presence related services to the user, Telephony Control Points (UPnP Telephony Devices) that initiate actions provided by the TS, And a telephony client device (TC) for media-dependent processing of input to and output from the TS and providing.

UPnP telephony services are based on Wide Area Network (WAN) calling technologies such as VOIP or other call technologies, using a telephony control point, enabling users to initiate calls/messages to or receive calls/messages from any user outside the UPnP home network Calls/messages from any user. For example, when a call is received from another device, a call notification is provided by the TS to the telephony control point. However, the UPnP telephony service does not provide call notification with incoming call status and originator address.

Contents of the invention

The present invention has been made to address at least the above problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention provides a method and system for providing enhanced event notification in a UPnP home network environment.

According to one aspect of the present invention, there is provided a method of providing an incoming event notification to a telephony control point in a UPnP home network environment. Information associated with the remote party is retrieved by the telephony server when an incoming event associated with the remote party arrives at the telephony server. Generates an incoming event notification associated with the incoming event. The incoming event notification includes information associated with the remote party. The incoming event is forwarded to at least one telephony control point in the UPnP home network environment together with the incoming event notification. When an incoming event arrives at a telephony control point, information associated with the remote party is displayed on a display of at least one telephony control point along with an incoming event notification.

According to another aspect of the present invention, there is provided a system comprising a telephony server and at least one telephony control point communicatively coupled to the telephony server via a UPnP home network. The telephony server is configured to: obtain information associated with the remote party when an incoming event is received from the remote party; generate an incoming event notification associated with the incoming event and having the information associated with the remote party; send the incoming event Forwarding to at least one telephony control point with the incoming event notification; and displaying information associated with the remote party with the incoming event notification.

According to still another aspect of the present invention, there is provided a method for providing user information in an outgoing call event in a UPnP home network environment. A request to initiate an outbound event for a remote party is received from a telephony control point. Get information associated with a user. An outbound event notification associated with the outbound event is generated using information associated with the user. Initiate outbound events and outbound event notifications to remote participants.

According to yet another aspect of the present invention, there is provided a system comprising: a telephony server; and at least one telephony control point communicatively coupled to the telephony server via a UPnP home network. The at least one telephony control point is configured to send a request to the telephony server to initiate an outbound event for the remote party. The telephony server is configured to obtain information associated with the user, generate an outgoing event notification associated with the outgoing event using the information associated with the user, and initiate the outgoing event and the outgoing event notification to the remote party, thereby when The user information and the notification of the outgoing event are displayed to the remote party when the outgoing event arrives at the remote party.

Description of drawings

The above and other aspects, features and advantages of the present invention will become more apparent from the following detailed description in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram of a UPnP home network system having a TS for providing enhanced event notification associated with an incoming event or an outgoing event, according to an embodiment of the present invention.

2 is a flowchart illustrating a method of providing enhanced incoming call notification indicating the arrival of an incoming call from a remote party to a telephony control point (TelCP), such as that shown in FIG. 1 , according to an embodiment of the present invention.

3 is a flowchart illustrating a method of providing enhanced inbound message notification indicating the arrival of an inbound message from a remote party to the TelCP, according to an embodiment of the present invention.

4 is a flowchart illustrating a method of providing an enhanced incoming session update notification indicating a session update from a remote party to a TelCP, according to an embodiment of the present invention.

5 is a flowchart illustrating a method of providing an outbound event notification associated with an intentional inbound event from a remote party, according to an embodiment of the present invention.

Figure 6 is a schematic representation of a telephony data model with a new element for storing preferences associated with incoming event notifications, according to an embodiment of the invention.

Figure 7 is a schematic representation of a telephony data model with a new element for storing configuration settings associated with outbound event notifications, according to an embodiment of the invention.

8A-8D are screenshot views of TelCP displaying enhanced incoming call notifications associated with incoming calls received from remote parties, according to an embodiment of the invention.

FIG. 9 is a block diagram showing various components of a TS such as that shown in FIG. 1 for implementing an embodiment of the present invention.

detailed description

Embodiments of the present invention are described in detail with reference to the accompanying drawings. The same or similar components may be designated by the same or similar reference numerals even when they are shown in different drawings. Detailed descriptions of constructions or processes known in the art may be omitted to avoid obscuring the subject matter of the present invention.

The present invention provides a method and system for providing enhanced event notification in a UPnP home network environment.

As used herein, the term "remote party" refers to an entity located outside the UPnP home networking environment and communicatively connected to a UPnP home device via a communication channel, such as a wireless area network. The terms "remote party information" and "information associated with a remote party" have the same meaning. And, the terms "user information" and "information associated with a user" have the same meaning.

FIG. 1 is a block diagram of a UPnP home network system 100 for providing enhanced event notifications associated with incoming events or outgoing events, according to an embodiment of the present invention. In FIG. 1 , UPnP home network environment 101 includes TS 102 , and TelCPs 104A-N connected to TS 102 via UPnP home network 108 . TS 102 is connected via WAN 110 to devices 106A-N associated with remote participants (eg, WAN users). TS 102 initiates communications between TelCPs 104A-N and remote party devices 106A-N.

For purposes of illustration, the following description is described with reference to TelCP 104A and remote party device 106A. Those skilled in the art will understand that the embodiments described here can be applied to the entire UPnP home network system 100 at the same time.

In operation, TS 102 receives incoming events (eg, calls, messages, updates, etc.) intended for TelCP 104A from remote party device 106A over WAN 110 . TS 102 obtains information associated with remote parties from various sources such as address book 112, presence service 114, and the like. The remote party information includes contact information, image information, location information, presence information, and/or service capabilities associated with the remote party.

TS 102 generates an incoming event notification including information associated with the remote party and forwards the incoming event to TelCP 104A along with the incoming event notification. Accordingly, TelCP 104A displays remote party information along with incoming event notifications.

In an embodiment of the invention, TS 102 sends remote party information to TelCP 104A as a Uniform Resource Locator (URL) in an incoming event notification. TelCP 104A uses the URL to retrieve remote party information from a backend server via an HTTP GET request and displays the remote party information on a display associated with TelCP 104A.

In an embodiment of the invention, TS 102 provides a link to a temporary document containing remote party information in an incoming event notification to TelCP 104A. TelCP 104A retrieves the temporary document from the backend server using the link given in the incoming event notification, and displays the remote party information in the temporary document.

In an embodiment of the present invention, TS 102 sends an incoming event notification to TelCP 104A using an image file or a hypertext markup language (HTML) page. TS102 includes remote party information in the remotepartyinfo element shown in Appendix 'A'. The remotepartyinfo element may be a peer (peer) type element. When an incoming event notification is received, TelCP 104A retrieves the remotepartyinfo element stored in TS 102 and displays the remote party information in the remotepartyinfo element along with the incoming notification indicating the arrival of the incoming event.

In an embodiment of the present invention, TS 102 provides incoming event notifications with remote party information to TelCP 104A via a dedicated push service of Call Management Service (CAMS). In one embodiment, TS 102 includes the information of the remote party in a pushinfoevent (push information event) state variable, and pushes the pushinfoevent state variable to TelCP 104A. TelCP 104A retrieves the remote party information from the pushinfoevent state variable and associates the remote party information with the incoming event based on the event type. Alternatively, TS 102 may include the caller identifier associated with the remote party in the pushinfoevent state variable along with the remote party information. Based on the caller identifier, TelCP 104A may associate remote party information with the incoming event based on the caller identifier. It may be noted that TS 102 may include the remote party information and/or caller identifier in the pushinfoevent state variable in the form of a URL, or an HTML document.

In another operation, TelCP 104A sends a request to TS 102 to initiate an outbound event (eg, call, message, or chat) for a remote party. TS 102 acquires information associated with the user of TelCP 104A based on the request. The user information includes contact information, image information, location information, presence information, and/or service capabilities associated with the remote party. TS 102 generates an outgoing event notification including the user's information, and sends the outgoing event to the remote party with the outgoing event notification. Accordingly, the device 106A associated with the remote party displays the user information in the outbound event notification. In this way, when a user initiates an outbound event to a remote party, the TelCP 104A may include information associated with the user in the outbound event initiation request so that the user information is displayed to the remote party regardless of whether the remote party subscribes to information associated with the user.

2 is a flowchart 200 illustrating a method of providing enhanced incoming call notification indicating the arrival of an incoming call from a remote party to the TelCP 104A, according to an embodiment of the present invention. At step 202, TS 102 receives an incoming call from remote party device 106A intended for TelCP 104A. In step 204, TS 102 obtains information associated with the remote party from various sources, such as address book 112, presence service 114, and the like. Information associated with remote participants includes contact information, image information, location information, presence information, and service capabilities.

At step 206, TS 102 includes the remote party's information in the incoming call notification associated with the incoming call. In an embodiment of the present invention, TS 102 includes remote party information in the callinfo (call information) state variable. The callinfo state variable is defined by CAMS, which provides a phone call experience to non-telephone home devices, to event out the arrival of an incoming call from a remote party to the TelCP 104A. In one embodiment, TS 102 includes information associated with the remote party in the remote party element of the callinfo state variable depicted in Appendix 'B'.

For example, remote party elements include image elements, location elements, service capability elements, and/or presence attribute elements. The image element includes image information in the form of a binary value representing an image of the remote party. The location element includes location information for the remote party. Location information can be included as an image, geolocation system coordinates, or plain text. The service capability element represents the service capability of the remote party. The presence attribute element includes presence information associated with the remote party. The presence attribute element includes a name attribute indicating a name of the presence attribute and a value indicating a value of the presence attribute.

The remote party element may be a peer-to-peer type element in which remote party information is included. An exemplary schema (schema) for equivalent type elements is provided in Appendix 'C'. The peer-type element contains information used to correctly identify the remote party associated with the incoming call. Additionally, if TS 102 supports telephony management profiles, TS 102 includes communications between a remote party and one or more contacts in the address book in the peer-to-peer type element.

In step 208, TS 102 sends an incoming call notification to TelCP 104A. At step 210, TelCP 104A displays the remote party information along with the incoming call notification on a display associated with TelCP 104A. The remote party information displayed on the TelCP 104A helps enhance the user's experience and enables additional service capabilities (eg, file transfers, video calls, etc.).

FIG. 3 is a flowchart 300 illustrating a method of providing enhanced notification of an incoming message indicating the arrival of an incoming message from a remote party to the TelCP 104A, according to an embodiment of the present invention. At step 302 , TS 102 receives an incoming message (eg, Short Message Service (SMS) message, email message, chat message, etc.) from remote party device 106A intended for TelCP 104A. In step 304, TS 102 obtains information associated with the remote party from various sources, such as address book 112, presence service 114, and the like. Information associated with remote participants includes contact information, image information, location information, presence information, and/or service capabilities.

At step 306, TS 102 includes the remote party's information in an incoming message notification associated with the incoming message. In an embodiment of the present invention, TS 102 includes remote party information in the newmessage (new message) state variable. The newmessage state variable is defined by the message service and is used to notify the arrival of a new incoming message from a remote party intended for TelCP 104A. The structure of the newmessage state variable is provided in Appendix 'D'. In some embodiments of the invention, the newmessage state variable includes a peer type element. In these embodiments, the peer type element contains information used to correctly identify the remote party associated with the incoming message. Additionally, if TS 102 supports telephony management profiles, TS 102 includes communications between a remote party and one or more contacts in the address book in the peer-to-peer type element.

In step 308, TS 102 sends the incoming message intended for TelCP 104A and the notification of the incoming message to TelCP 104A. At step 310, TelCP 104A displays the remote party information along with the incoming message notification on a display associated with TelCP 104A. The remote party information displayed on the TelCP 104A helps improve the user's experience and enables additional service capabilities.

FIG. 4 is a flowchart 400 illustrating a method of providing enhanced incoming session update notifications indicating session updates from a remote party to TelCP 104A, according to an embodiment of the present invention. At step 402, TS 102 receives an incoming session update intended for TelCP 104A from remote participant device 106A. At step 404, TS 102 obtains information associated with the remote party. Information associated with remote participants includes contact information, image information, location information, presence information, and service capabilities.

At step 406, TS 102 includes information associated with the remote party in the incoming session update notification. In an embodiment of the invention, TS 102 includes remote party information in session update state variables. A session update state variable is defined by a messaging service to notify TelCP 104A of changes to an ongoing chat session or an incoming chat session between a remote party and a party. A session update state variable includes a session identifier and session state information. In some embodiments of the invention, the session update state variable includes a peer type element. In these embodiments, the peer type element is included to correctly identify the remote party associated with the incoming session update. Additionally, if TS 102 supports telephony management profiles, TS 102 includes communications between a remote party and one or more contacts in the address book in the peer-to-peer type element.

In step 408, TS 102 sends an incoming session update and an incoming session update notification intended for TelCP 104A to TelCP 104A. At step 410, TelCP 104A displays the remote party information along with the incoming session update notification on a display associated with TelCP 104A. The remote party information displayed on the TelCP 104A helps improve the user's experience and enables additional service capabilities.

Alternatively, TelCP 104A may retrieve session updates associated with ongoing or new chat sessions by calling the GetSessions() action. The GetSession() action returns a SessionList as shown in Appendix 'E' that includes remote party information associated with the session update.

From the foregoing description, embodiments of the present invention allow a user to set preferences for displaying information associated with a remote party when an incoming event arrives at TelCP 104A. TS 102 stores preferences in the telephony data model. Referring to Figure 6, the telephony data model 600 includes a new element 'EnhancedNotification' ('EnhancedNotification') 602 for storing settings for displaying remote party information during the arrival of an incoming event. For example, the new element 'Enhanced Notification' 602 stores the values 'Image', 'Location', 'Presence', and/or 'None' as preferences set by TelCP 104A. Thus, depending on the value set in the new 'Enhanced Notification' element 602, TS 102 includes information associated with the remote party in the incoming event notification. When the value of the new 'Enhanced Notification' element 602 is set to 'none', the TS 102 will not include information associated with the remote party in the incoming event notification. In addition, CMS actions are used to manipulate new elements in the telephony data model.

FIG. 5 is a flowchart 500 illustrating a method of providing an outbound event notification associated with an intentional inbound event from a remote party, according to an embodiment of the present invention. At step 502, TelCP 104A sends a request to TS 102 to initiate an outbound event (eg, call, message, or chat) for a remote party. At step 504, TS 102 retrieves information associated with the user based on the request. For example, TelCP 104A may request TS 102 to include subscriber information in the outbound event notification through the StartCall() action. The StartCall() action may include the following arguments:

The "MediaCapabilityInfo" argument allows TelCP 104A to specify the media capability associated with TelCP 104A in an outbound event notification, according to an embodiment of the present invention. An exemplary structure of the Media Capability Information is provided in Appendix 'F' and extensions to the Media Capability Information are provided in Appendix 'G'. In another embodiment of the invention, the StartCall() action includes a new argument for including user information in the outbound event notification.

In yet another embodiment of the invention, TS 102 maintains configuration settings such that TelCP 104A does not need to include information in StartCall(). Therefore, when TelCP 104A includes the StartCall() action in the outgoing event initiation request, TS 102 includes user information in the outgoing event notification. In one embodiment, TS 102 stores configuration settings in a telephony data model. Referring to Figure 7, the telephony data model 700 includes a new element 'Enhanced Outgoing Session' ('Enhanced OutgoingSession') 702 for storing configuration settings to include user information in outgoing event notifications. For example, a new element 'Enhanced Outgoing Session' 702 stores the values 'Image', 'Location', 'Presence', or 'Service Capabilities' as configuration settings. Thus, depending on the value set in new element 702, TS 102 includes information associated with the subscriber in the outbound event notification. When the value of the new element 'Enhanced Outgoing Session' 702 is set to 'empty', TS 102 will not include information associated with the user in the outbound event notification.

Referring to FIG. 5, at step 506, TS 102 sends the outbound event to the remote party along with the outbound event notification. The outbound event notification includes information associated with the user, where the user information includes contact information, image information, location information, presence information, and/or service capabilities. At step 508, the display device associated with the remote party displays the user information in the outbound event notification. In this manner, when a user initiates an outbound event to a remote party, TelCP 104A may include information associated with the user in the outbound event initiation request so that the user information is displayed to the remote party regardless of the remote party's Whether to subscribe to the information associated with the user.

8A-8D are screenshot views of the TelCP 104A displaying enhanced incoming call notifications associated with incoming calls received from remote parties, according to an embodiment of the invention. As described above, when TS 102 receives an incoming call to TelCP 104A from a remote party, TS 102 obtains information such as contact information, image, location, presence status, service capabilities from various sources such as address book 112, presence service 114, etc. information and include it in the incoming call notification. And, TS 102 forwards the incoming call to TelCP 104A together with the enhanced incoming call notification. In FIG. 8A, TelCP 104A displays the remote party's image along with the remote party's email ID as additional information. In FIG. 8B, TelCP 104A displays the remote party's image and location information along with the remote party's email ID. In FIG. 8C, TelCP 104A displays the remote party's image and service capability information along with the remote party's email ID. In Figure 8D, the TelCP 104A displays the remote party's image and presence information (eg, 'feeling sad (feeling sad)!!!') along with the remote party's email ID.

FIG. 9 is a block diagram illustrating various components of a TS 102 such as that shown in FIG. 1 for implementing an embodiment of the present invention. In FIG. 9 , TS 102 includes processor 902 , memory 904 , read only memory (ROM) 906 , transceiver 908 , bus 912 , communication interface 910 , display 914 , input device 916 , and cursor control 918 .

Processor 902 as used herein refers to any type of computing circuitry such as, but not limited to, microprocessors, microcontrollers, complex instruction set computing microprocessors, reduced instruction set computing microprocessors, very long instruction word Microprocessors, explicit parallel instruction computing microprocessors, graphics processors, digital signal processors, or any type of processing circuitry. Processor 902 may also include embedded controllers, such as general-purpose or programmable logic devices or arrays, application-specific integrated circuits, single-chip computers, smart cards, and the like.

Memory 904 can be both volatile and non-volatile memory. The memory 904 includes an event notification module 920 stored therein in the form of instructions to provide enhanced event notification in the UPnP home networking environment 100, according to an embodiment of the present invention. A variety of computer-readable storage media may be stored in or accessed from the memory element. The memory elements may include any suitable memory device for storing data and machine-readable instructions, such as read-only memory (ROM), random-access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable Programmable Read Only Memory (EEPROM), Hard Disk Drives, Removable Media Drives for handling memory cards, Memory Stick™, and more.

Embodiments of the invention may be implemented in conjunction with modules including functions, procedures, data structures, and application programs for performing tasks or defining abstract data types or low-level hardware contexts. Machine-readable instructions stored on any of the storage media described above may be executed by processor 902 . For example, a computer program may include machine-readable instructions capable of providing enhanced event notifications in the UPnP home networking environment 100 according to embodiments of the present invention. In one embodiment of the invention, the computer program may be included on a storage medium and loaded from the storage medium to a hard drive in non-volatile memory.

Components such as transceiver 908, communication interface 912, display 914, input device 916, and cursor control 918 are well known to those skilled in the art.

Various devices, modules, selectors, estimators, etc. can be enabled and operated using hardware circuitry such as complementary metal oxide semiconductor (CMOS) based logic, firmware, software, and/or hardware, Any combination of firmware, and/or software embodied in a machine-readable medium. For example, various electronic structures and methods may be embodied using transistors, logic gates, and electronic circuits such as application specific integrated circuits.

Although the present invention has been described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit of the invention as defined in the appended claims. spirit and scope.

[Appendix 'A']

[Appendix 'B']

[Appendix 'C']

[Appendix 'D']

[Appendix 'E']

[Appendix 'F']

[Appendix 'G']

Claims (12)

1. A method for providing incoming event notifications to a telephony control point in a Universal Plug and Play (UPnP) home network environment, comprising the steps of: receiving, by the telephony server, an incoming event associated with the remote party; obtaining, by the telephony server, information associated with the remote party, the information being stored in the telephony server or other device; generating an incoming event notification associated with the incoming event, the incoming event notification including information associated with the remote party; The incoming event is forwarded to at least one telephony control point in the UPnP home network environment together with the incoming event notification. 2. The method of claim 1, wherein the information associated with the remote party includes at least one of contact information, image information, location information, presence information, and service capabilities. 3. The method of claim 1, wherein the incoming event is associated with a call service and a message service. 4. The method of claim 1, further comprising: receiving a request from a telephony control point to initiate an outbound event for a remote party; Obtain information associated with a user; generating an outbound event notification associated with the outbound event utilizing information associated with the user; and Initiate outbound events and outbound event notifications to remote participants. 5. The method of claim 4, wherein the information associated with the user includes at least one of contact information, image information, location information, presence information, and service capabilities. 6. The method of claim 4, wherein the outbound event is associated with a call service and a message service. 7. A telephone server, comprising: transceiver; memory, including at least one storage medium storing machine-readable instructions; and at least one processor, wherein when the transceiver receives an incoming event from a remote party, the at least one processor executes machine-readable instructions to cause the telephony server to perform the steps of: obtaining information associated with a remote party when an incoming event is received from the remote party, the information being stored in a telephony server or other device; generating an incoming event notification associated with the incoming event and having information associated with the remote party; The incoming event is forwarded to at least one telephony control point together with the incoming event notification. 8. The telephony server of claim 7, wherein the information associated with the remote party includes at least one of contact information, image information, location information, presence information, and service capabilities. 9. The telephony server of claim 7, wherein the incoming event is associated with a call service and a message service. 10. The telephony server of claim 7, wherein when the transceiver receives a request from a telephony control point to initiate an outbound event for a remote party, said at least one processor executes machine-readable instructions to cause the telephony server to perform steps : Obtain information associated with a user; generating an outbound event notification associated with the outbound event utilizing information associated with the user; and An outbound event and an outbound event notification are initiated to the remote party such that information associated with the user and the outbound event notification are displayed to the remote party when the outbound event reaches the remote party. 11. The telephony server of claim 10, wherein the information associated with the user includes at least one of contact information, image information, location information, presence information, and service capabilities. 12. The telephony server of claim 10, wherein the outbound event is associated with a call service and a message service.