Method and apparatus for exchange of information in a communication network

• US 7,929,470 B2
• Filed: 01/18/2001
• Issued: 04/19/2011
• Est. Priority Date: 01/19/2000
• Status: Expired due to Fees

• Current Assignee: Sony Corporation (Sony Group Corp.)
• Original Assignee: Sony Ericsson Mobile Communications USA Incorporated (Sony Group Corp.)
• Inventors: Pohjanvuori, Timo, Minborg, Per-Åke
• Primary Examiner(s): Ngo; Ricky
• Assistant Examiner(s): SAMUEL, DEWANDA A
• Application Number:
  US10/169,414
• Publication Number:
  US 20030135586A1
• Time in Patent Office: 3,743 Days
• Field of Search: 370/352, 370/338, 370/354, 370/353, 370/300, 370/356, 370/260
• US Class Current: 370/300
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/10015 Access to distributed or replicated servers, e.g. using brokers
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 1/2535 adapted for voice communication over an Internet Protocol [IP] network Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16
• CPC Class Codes: H04M 1/57 Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set at the operator set in a manual exchange H04M5/20
• CPC Class Codes: H04M 1/72445 for supporting Internet browser applications
• CPC Class Codes: H04M 2203/651 Text message transmission triggered by call automatic reactions in messaging within packet-switching networks H04L51/02
• CPC Class Codes: H04M 2203/658 Combination of voice calls and paging
• CPC Class Codes: H04M 2207/18 wireless networks
• CPC Class Codes: H04M 2242/22 Automatic class or number identification arrangements
• CPC Class Codes: H04M 3/02 Calling substations, e.g. by ringing selective calling H04Q
• CPC Class Codes: H04M 3/42042 Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42059 : Making use of the calling party identifier
• CPC Class Codes: H04M 3/42093 : Notifying the calling party of information on the called or connected party
• CPC Class Codes: H04M 3/42102 : Making use of the called party identifier
• CPC Class Codes: H04M 3/42382 : Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
• CPC Class Codes: H04M 7/0036 : where the data service is an information service
• CPC Class Codes: H04M 7/006 : Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/1235 : where one of the core networks is a wireless network
• CPC Class Codes: H04M 7/128 : Details of addressing, directories or routing tables
• CPC Class Codes: H04Q 2213/13091 : CLI, identification of calling line
• CPC Class Codes: H04Q 2213/13098 : Mobile subscriber
• CPC Class Codes: H04Q 3/72 : Finding out and indicating number of calling subscriber
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/18 : Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 76/20 : Manipulation of established connections
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/00 : Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/18 : between terminal devices

Abstract

A technique for connecting a unique identifier to a data object is described. The connecting of a unique identifier such as a telephone number or an internet address such as an IPv6 address, to a specific data object, hereafter referred to as phonepage, will allow an A-party direct access to information that a B-party or B-party user equipment wishes to display to a connecting party. The phonepage resides in a memory in a telecommunications or data network. The phonepage may have a similar appearance to an Internet web page, but may also take other appearances. The displaying or processing of the phonepage may be made dependent upon the capabilities of the A-party user equipment.

Claims

1. A method of retrieving information related to communication events, comprising:

determining the occurrence of a triggering event associated with a communication service between a first user communication application at a first user device and a second user communication application at a second user device;

assembling a data object request comprising a first parameter representing a communication service address associated with the second user communication application and a second parameter indicating which of a plurality of triggering events is determined;

sending the data object request to a data object server;

receiving, at the first user device, a data object corresponding to the first and second parameters of the data object request; and

processing the received data object.

2. The method of claim 1, wherein the communication service is a data communication service.

3. The method of claim 2, wherein the communication service address comprises one of an e-mail address, an IPv4 address, a SIP address, or an IPv6 address.

4. The method of claim 1, wherein sending the data object request to a data object server comprises:

determining a server address based on one or more of a type of the communication service, a service provider of the communication service, or the geographic location of the first user communication application; and

sending the data object request to the server address.

5. The method of claim 1, wherein the data object request further comprises one or more of:

a third parameter indicating one or more communication types available to the first user communication application;

a fourth parameter representing a priority of use for one or more of the communication types available to the first user communication application; and

a fifth parameter representing a code indicating a type of communication service established with the second user communication application; and

wherein the data object received at the first user device further corresponds to one or more of the third, fourth, and fifth parameters.

6. The method of claim 1, wherein the data object request further comprises a third parameter indicating an identity associated with the first user communication application, and wherein the data object received at the first user device further corresponds to the third parameter.

7. The method of claim 1, wherein the data object request further comprises a third parameter indicating the availability of an accessory device associated with the first user communication application, wherein the data object received at the first user device is adapted to the accessory device, and wherein processing the received data object comprises processing the received data object using the accessory device.

8. The method of claim 1, wherein the data object request further comprises a third parameter indicating a capability of the first user device, wherein the data object received at the first user communication application is adapted to the indicated capability, and wherein processing the received data object comprises processing the received data object according to the indicated capability.

9. The method of claim 1, wherein the received data object comprises a network address, and wherein processing the received data object comprises retrieving information using the network address.

10. The method of claim 9, wherein retrieving information using the network address comprises initiating an Internet browser application and using the Internet browser application to retrieve content from a server corresponding to the network address, and wherein the method further comprises displaying the retrieved content.

11. The method of claim 1, wherein the received data object comprises information associated with the second user communication application, and wherein processing the received data object comprises updating phonebook information associated with the first user communication application.

12. A user device for use with a communication system, wherein the user device is configured to:

determine the occurrence of a triggering event associated with a communication service between a first user communication application associated with the user device and a second user communication application associated with a remote user device;

assemble a data object request for a data object comprising a first parameter representing a communication service address associated with the second user communication application and a second parameter indicating which of a plurality of triggering events is determined;

send the data object request to a data object server;

receive, in response to the data object request, a data object corresponding to the first and second parameters of the data object request; and

process the received data object.

13. The user device of claim 12, wherein the user device comprises a mobile telephone.

14. The user device of claim 12, wherein the received data object comprises a network address, and wherein the user device is configured to process the received data object by retrieving information using the network address.

15. The user device of claim 12, wherein the received data object comprises information associated with the remote device, and wherein the user device is configured to process the received data object by updating phonebook information at the user device.

16. The user device of claim 12, wherein the data object request further comprises a third parameter indicating the availability of an accessory device associated with the user device, wherein the received data object is adapted to the accessory device, and wherein the user device is configured to process the received data object using the accessory device.

17. A data object server for use in a communication system, configured to:

receive a data object request comprising a first parameter representing an address associated with a first user communication application at a first user device and a second parameter representing a triggering event associated with communication between the first user communication application and a second user communication application at a second user device;

select a data object based on the first and second parameters from a plurality of data objects associated with the first parameter; and

send a message based on the selected data object to the second user device.

18. The data object server of claim 17, wherein the data object request comprises a third parameter indicating a capability of the second user device, wherein the data object server is further configured to adapt the selected data object according to the indicated capability, and wherein the message based on the selected data object comprises the adapted data object.

19. The data object server of claim 17, wherein the data object request comprises a third parameter indicating the availability of an accessory device associated with the second user device, wherein the data object server is further configured to adapt the selected data object according to the indicated accessory device, and wherein the message based on the data object comprises the adapted data object.