Method and apparatus for exchange of information in a communication network

• US 20030135586A1
• Filed: 09/04/2002
• Published: 07/17/2003
• Est. Priority Date: 01/19/2000
• Status: Active Grant

• Current Assignee: Sony Corporation (Sony Group Corp.)
• Original Assignee: Sony Ericsson Mobile Communications USA Incorporated (Sony Group Corp.)
• Inventors: Pohjanvuori, Timo, Minborg, Per-Ake
• Granted Patent: US 7,929,470 B2
• Time in Patent Office: Days
• US Class Current: 709/219
• 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 a data object to a first user communication application in connection with establishment of a communication service with a second user communication application, characterized in that the method comprising in the first user communication application the following steps:

determining an occurance of a triggering event;

acquiring a communication service address associated with the triggering event;

assembling a request for a data object associated with the communication service address, the request comprising at least two parameters, a first parameter representing the communication service address and a second parameter representing the determined triggering event;

sending the request for the data object to a data object server;

receiving the data object or an indication of the data object from the data object server in view of the parameters;

processing the received data object or indication of the data object.

2. The method according to claim 1, characterized in that the type of communication service determines the data object server.

3. The method according to claim 1, characterized in that a service provider of the communication service, determines the data object server.

4. The method according to claim 1, characterized in that the data object server is predetermined.

5. The method according to claim 1, characterized in that the geographical location, such as the country of registration, of the first user communication application determines the data object server.

6. The method according to any one of claims 1 to 5, characterized in that the communication service address is also associated with second user communication application.

7. The method according to any one of claims 1 to 6, characterized in that a parameter of the request is a representation of a code indicating which communication types are available to the first user communication application.

8. The method according to any one of claims 1 to 7, characterized in that a parameter of the request is a representation of a code indicating a priority of use of the communication types available to the first user communication application.

9. The method according to any one of claims 1 to 8, characterized in that a parameter of the request is a representation of a code indicating the desired communication service aith the second user communication application.

10. The method according to any one of claims 1 to 9, characterized in that the communication service address is an access address of the first user equipment.

11. The method according to any one of claims 1 to 9, characterized in that the communication service address is an access address of the second user equipment.

12. The method according to any one of claims 1 to 11, characterized in that the first user communication application is an originating application and the second user communication application is a terminating application.

13. The method according to any one of claims 1 to 11, characterized in that the second user communication application is an originating application and the first user communication application is a terminating application.

14. The method according to any one of claims 1 to 13, characterized in that a parameter of the request is a representation of a code indicating data bearer type.

15. The method according to any one of claims 1 to 14, characterized in that a parameter of the request is a representation of a code indicating the type of the user equipment of the first or the second user communication application.

16. The method according to any one of claims 1 to 15, characterized in that a parameter of the request is a representation of a code indicating an available and/or attached accessory.

17. The method according to any one of claims 1 to 16, characterized in that a parameter of the request is a representation of a code indicating the version of the method.

18. The method according to any one of claims 1 to 17, characterized in that the request is encrypted before sending.

19. The method according to any one of claims 1 to 18, characterized in that the received data object is encrypted and in that the step of processing comprises decryption of the data object.

20. The method according to any one of claims 1 to 19, characterized in that the triggering event is comprises an event of an outgoing communication being or is about to be initiated.

21. The method according to any one of claims 1 to 20, characterized in that the step of determining a triggering event further determines if there are any additional triggering events during the time a communication is being conducted to thereby be able to initiate further data object requests during the communication.

22. The method according to any one claims 1 to 21, characterized in that the triggering event is an event of a designated button on a user equipment being pressed.

23. The method according to any one of claims 1 to 22, characterized in that a parameter of the request is a representation of a code identifying a data object server.

24. The method according to claim 23, characterized in that the representation of a code identifying a data object server represents a server name or a plain IP address.

25. A telecommunication system comprising a first user equipment with a first user communication application, a second user equipment with a second user communication application, and a communication network to establish a communication service channel between the first user application and the second user application, and a data object server, characterized in that the first user equipment is arranged to determine the occurance of a triggering event, acquire a communication service address associated with the triggering event, and assemble a request of a data object associated with the communication service address, the request comprising at least two parameters, a first parameter representing the communication service address and a second parameter representing the determined triggering event, and is arranged to send the request for the data object to the data object server, and in that the data object server is arranged to return the data object or an indication of the data object in view of the parameters to the first user application in response to the request, and in that the first user equipment is arranged to receive the data object or the indication of the data object from the data object server and to then process the received data object or the indication of the data object.