WO2008155460A1

WO2008155460A1 - A method for providing a communication connection, a database of communication attributes, and a terminal or other network element using commnuciation attributes

Info

Publication number: WO2008155460A1
Application number: PCT/FI2008/050366
Authority: WO
Inventors: Lauri Isotalo; Tuomo Rostela
Original assignee: Elisa Oyj
Priority date: 2007-06-20
Filing date: 2008-06-16
Publication date: 2008-12-24
Also published as: FI120995B; FI20075475A; FI20075475A0

Abstract

A method according to the invention is intended to create a communication connection between the terminal devices of an originator and a recipient. The method comprises the following steps to be executed in a telecommunication network. The connection-attribute query initiated by the originator is received in the telecommunication network, and a query to the connection attribute database is transmitted. Subsequently, the connection attributes associated with the recipient are obtained from the connection attribute database by using a data set denoted by the connection-attribute query, whereby the connection attributes contain at least one of the following data related to the terminal device: Type of access network, connection speed, QoS (Quality of Service) class, connection fee, terminal device capability set, [and] communication application data. The acquired connection attributes are transmitted to the originator's terminal device, whereupon the connection modes determining the connection attributes related to the selection sent from the originator's terminal device are received in the telecommunication network. Finally the communication connection between the originator's and the recipient's terminal devices is created in the telecommunication network according to the selection.

Description

A method for providing a communication connection, a database of communication attributes, and a terminal or other network element using communication attributes

Field of the invention

[001] The invention relates to the creation of a communication connection between terminal devices in a telecommunication network such that a connection mode may be selected, when these terminal devices support several connection modes. The invention, furthermore, relates to IP (Internet Protocol) connections and ENUM (tElephone Number Mapping) queries-

Background of the invention

[002] In the early days of telecorπ^'munication, a telephone connection was the only way of communicating between parties. After the invention of the fax machine, instead of a telephone connection, fax transmissions became possible.

[003] The advent of mobile communication networks enabled telephone connections not only within a mobile communication network, but also from a mobile communication network to a fixed network (landline), and vice versa. Moreover, mobile communication networks made possible a new connection mode, i.e., sending a text message.

[004] The Internet brought along electronic mail and the downloading of files from the Internet to a terminal device. If the communication parties use VoIP (voice over internet protocol) telephones, they may call each other and talk over the Internet. [005] Currently the merging of various types of communication networks is underway. The IP protocol known from the Internet is becoming more common in trunk networks, which may transmit simultaneously a fixed- network, mobile-communicatioπ-πetwork and Internet traffic as IP packets. [006] E.164 is the standard created by ITU (International Telecommunication Union) for international and international telephone numbers. The standard is generally used in all telephone communication. The E.164 number refers to a telephone number according to the E.164 standard, i.e., a fixed-network number or mobile-communication number. [007] The E.164 number may be converted to an IP address. This subject is explained especially in IETF (Internet Engineering Task Force) document RFC 3761. The conversion of the E.164 number to an IP-network address involves three steps, which may be designated as follows: 1 ) complete domain name creation, 2) ENUM query, and 3) DNS query. [008] In the first step, the sequence of the individual numerical characters in the E.164 number is translated, the other characters removed, and each numerical character separated from the other numerical characters by a point. Finally, another root identifier "e164.arpa" is added to the end. [009] For instance, the E.164 number +358501234567 is converted in the ENUM conversion to the following character string: 7.6.5.4.3.2.1.0.5.8.5.3.e164.arpa. [010] The character string is designated as an FQDN (Fully Qualified Domain Name).

[011] Figure 1 shows an example of an ENUM query and a DNS query. The ENUM query uses the FQDN obtained in the first step of the search related to the ENUM database. As its result, the query produces one or more NAPTR (naming authority pointer) records.

[012] It is assumed that the terminal devices 101 and 102 are VoIP phones, and that the user of terminal device 101 wishes to call a VoIP phone. [013] First, the terminal device (or network element) 101 converts the VoIP phone to the FQDN of the recipient's E.164 number. More specifically, the receiver's E.164 number converts the terminal device belonging to recipient 102 to FQDN 103. Then the terminal device 101 sends the FQDN 103 through the telecommunication network 104 to the ENUM-database server 105.. Server 105 uses FQDN 103 as a search key, and obtains from the ENUM database one or more NAPTR records 106, which it sends through telecommunication network 104 to terminal device 101.

[014] It is assumed that FQDN 103 is the above-mentioned: 7.6.5.4.3.2.1.0.5.8.5.3.e164.arpa.

Thus, the following three NAPTR records are obtained by FQDN 103 from the ENUM database: sip: ville.virtanen@pulinakaista.fi e-mail: ville.virtanen@pulinakaista.fi phone: +358501234567

[015] The first NAPTR record indicates that terminal device 102 supports the SIP protocol (Session Initiation Protocol), which is an important but not an exclusive requirement for a VoIP phone or a video connection. [016] The two latter NAPTR records indicate that the recipient (ViIIe Virtanen) may send electronic mail, and that the recipient may try to reach the telephone number.

[017] Since the above assumes that the user of terminal device 101 wishes to call a VoIP phone, the first NAPTR record is used in the DNS query. More accurately put, terminal device 101 reads the domain name 107, i.e., pulinakaista.fi, from the NAPTR record, and sends domain name 107 through telecommunication network 104 to DNS server 108, whereby the DNS server sends an IP address 109 corresponding to the domain name 107 to terminal device 101. The IP address 109, the result to be produced by the ENUM query, indicates the IP address of the SIP server, where the 102 IP address of the terminal device may be retrieved. After retrieval, the user may call terminal device 102 of the VoIP phone using terminal device 101. [018] The prior-art ENUM database thus contains certain data needed for creating the communication connection, such as domain names, E.164 numbers, and telecommunication protocols. The telecommunication protocols are explained in the following, based on the NAPTR records explained above. [019] The first NAPTR record contains the notation "sip:," and the telecommunication protocol is therefore SIP.

[020] The second NAPTR record contains the notation "e-mail," and the telecommunication protocol is therefore MailTo.

[021] The third NAPTR record contains the notation "phone: +358...," so it may be determined that the relevant E.164 number is a Finnish telephone number. By using the Finnish numbering scheme, the operator associated with the E.164 number may also be determined.

[022] The domain names to be contained in the ENUM database and the E.164 numbers may be designated as their Internet addresses. [023] The first prior-art problem is that sometimes only incomplete or unreliable data may be obtained from the data-communication protocol associated with the Internet address. Hence, the creation of a communication connection may fail.

[024] The second prior-art problem is that the terminal device user or "originator" considering a communication connection does not know through which (one or several) Internet address(es) the recipient may be reached at precisely that moment. [025] The publication WO 2006/113217 A1 offers a solution to the second prior-art problem.

[026] The publication WO 2006/113217 A1 discloses a method, in which so-called recipient status data or "presence information" is retrieved from a server connected to a telecommunication network. The recipient status data are obtained from the status database via a server.

[027] The status database contains a notation for each Internet address of the recipient, whereby each Internet address is either a domain name or an E.164 number. The notation indicates whether the recipient at that moment may be reached through a certain Internet address.

[028] The status database associated with the recipient (ViIIe Virtanen) described above may contain the following notations: sip: ville.virtanen@pulinakaista.fi — Unavailable e-mail: ville.virtanen - Available phone: +358501234567 - Unavailable

[029] These notations indicate that the recipient at that moment is only available by e-mail, i.e., through the Internet address ville.virtanen@elisa.fi. [030] In one embodiment of the method, the ENUM-database server sends a request to the status server. The request contains all the recipient's Internet addresses found in the ENUM database.

[031] Upon this request, the status server retrieves the recipient's Internet addresses from the status database and the "Available" or "Unavailable" notations associated therewith. Then, in response to the request, the status server sends the recipient's Internet addresses and their notations to the ENUM-database server.

[032] The ENUM-database server forms a subset from the recipient's Internet addresses such that the subset contains the Internet addresses associated with the "Available" notation. According to the example provided above, the subset for the recipient's (ViIIe Virtanen's) Internet addresses will contain one Internet address, i.e., ville.virtanen@elisa.fi.

[033] Finally, the ENUM-database server sends the subset for the recipient's Internet addresses to the terminal device, where the user is trying to reach the recipient. [034] The ENUM database and the method of the publication WO 2006/113217 A1 , however, do not solve all the relevant problems. [035] The third prior-art problem is that the originator does not necessarily know what kind of communication connection is possible for the recipient's terminal device.

[036] In the early days of fixed networks, calling a fixed-network telephone number was the only possible connection mode. Currently, there are at least the following connection modes: Calling an E.164 number, a VoIP connection, data connection, video connection, electronic mail, fax, and instant messaging. Sending text messages and MMS (multimedia messaging service) are some examples of instant messaging. There is a spectrum of different of connection modes available especially to data connections, video connections, and instant messaging.

[037] The originator may, of course, experiment with connection modes. If the originator knows that the recipient's terminal device supports the SIP protocol, he may try calling the video connection for the recipient's terminal device. However, the SIP protocol support does not guarantee that the communication connection to the recipient's terminal device may be established or that the communication connection will work flawlessly. [038] Experimenting with the connection mode is time-consuming, and unsuccessful attempts to create a connection will frustrate the originator, as will poor communication connections. The billing systems of the telecommunication networks are generally such that even poor communication connections will be charged for. The unreliability of the connection modes diminishes the users' interest in the services provided by a telecommunication network. Thus, the unreliability of connection modes impedes the business activity of network operators, service operators, and service providers.

[039] The technical problem of the invention is that the terminal device of the telecommunication network is unable to propose to its user, which connection modes are in fact possible for (a) certain terminal device(s).

Summary of the invention

[040] One aspect of the invention is to solve the problem described above. [041] A second aspect of the invention is the so-called collection of connection attributes for the connection attribute database. The connection attributes describing certain capabilities of the terminal device contain at least one of the following data: The access network type, connection speed, QoS (Quality of Service) class, the connection fee, the terminal device capability set, or communication application data, such as name and version number.

[042] An access network refers to a network to which a terminal device is connected at that moment, and through which, the user of the terminal device may be reached. The terminal device may be connected simultaneously to several access networks. The above-mentioned connection attributes "maximum connection speed" and "QoS class" may apply to different access networks.

[043] Certain typical communication applications are available only in certain access networks. Sometimes creating a communication connection between terminal devices requires that the terminal devices use a communication application of the same name.

[044] Another aspect of the invention is the distribution of the connection attributes from the connection attribute database through the telecommunication network to the terminal devices, so that each terminal device is able to propose to its user which connection modes for other terminal devices are in fact possible.

[045] The connection attributes may be distributed in push-service type fashion on all terminal devices belonging to the same group. Alternatively, connection attributes may be transmitted to the terminal device in response to the connection-attribute query initiated by the terminal device.

[046] Each possible connection mode determines at least one connection attribute obtained from the connection attribute database. In general, several connection attributes determine one connection mode. [047] A further aspect of the invention is that besides the connection attributes describing the capabilities of the terminal devices, other connection attributes associated with the users, e.g., address information, may be stored in the connection attribute database.

[048] The connection attribute database is a centralized or distributed database. If the connection attribute database is distributed, its sections may possibly belong to different network or service operators.

[049] A further aspect of the invention is finding the right connection attribute database or its distributed section when the specific connection attributes need to be sent to the terminal device. [050] The invention comprises: 1 ) a method for creating a communication connection in a telecommunication network between the terminal devices of the originator and recipient, 2) improving the accessibility of the recipient's connection attribute database, and 3) a terminal device and 4) network element using the connection attributes stored in the connection attribute database.

Brief description of drawings

[051] The invention is described in more detail below in reference to the attached schematic figures, in which

Figure 1 shows the known ENUM query and DNS query;

Figure 2A presents an example of a window intended for selection of connection mode;

Figure 2B shows an example of choosing the connection mode on the menu referred to;

Figure 3 shows an embodiment of the invention; Figure 4A shows a method for creating a communication connection;

Figure 4B shows the additional steps for the ENUM query; Figure 4C shows two additional steps for creating the connection- attribute query, which steps are interchangeable; Figure 4D shows the additional steps for updating the connection attribute database;

Figure 4E shows a method for a second embodiment; Figure 5A shows an embodiment of the invention, in which the connection-attribute query comes from an ENUM- database server; Figure 5B shows an embodiment of the invention, in which the connection-attribute query comes from an intelligent network server; Figure 5C shows an embodiment of the invention, in which the connection-attribute query comes from a push service provided by a server; Figure 5D shows an embodiment of the invention, in which the server containing the connection attribute database is a push server;

Figure 6 shows a connection attribute database; Figure 7 shows a terminal device using connection attributes; Figure 8 shows a network element using connection attributes; Detailed description of the invention

[052] In order to utilize the invention, the user needs a suitable terminal device. A terminal device refers to a device containing at least telecommunication means, means for processing connection attributes, and a display. The means for processing connection attributes lack the known terminal devices, but many different-type terminal devices may be added thereto. The type of terminal device may be one of the following: A mobile telephone, PDA (personal digital assistant), desktop computer, or a portable computer. [053] The terminal device should contain telecommunication means enabling it to receive connection attributes related to other terminal means and send its own connection attributes to the connection attribute database. [054] The terminal device should contain telecommunication processing devices enabling it to process its own connection attributes and connection attributes related to other terminal devices, and determine the connection modes based on the processed connection attributes. [055] The terminal device should contain a display in order to show the connection modes to a user of the terminal device. The display may show various types of user-interface elements such as windows, icons, menus and options.

[056] Figure 2A shows an example of how to select the connection mode on the window referred to. On its touch screen, the user terminal device shows window 201 containing six icons. The image text of three of these icons 202-204 is bold-faced, and the image text of the remaining icons is italicized.

[057] The user's terminal device supports all six connection modes shown in window 201 , however, the recipient's terminal device supports only the connection modes associated with windows 202-204. Thus, icons 202-204 show the possible [available] connection modes to the recipient's terminal device, whereby the user may select the most suitable connection mode by touching the appropriate icon.

[058] The user may also be given the option of examining the connection modes associated with icons 202-204. In this way, the user sees the connection attributes associated with a certain connection mode, and may assess whether the selectable connection mode matches expectations. [059] Instead of a touch screen, it is possible to use a display in the terminal device, whereby pointing is done with a mouse. [060] The use of the invention is not limited to certain types of displays or display-pointing means. [061] Figure 2B shows an example of how to select the connection mode on the menu referred to. It is assumed that the user of the mobile phone has entered the recipient's number as 0501234567, and then pressed the mobile- phone key that initiates the communication connection. [062] Subsequently, the mobile phone shows the possible connection modes to the recipient's terminal device as options 207-209 on menu 206, and whose number is 0501234567. The user of the mobile phone may select whether to make a GSM call using option 207, a VoIP call using option 208, or a video call using option 209. [063] These connection modes each have advantages and disadvantages, which the user weighs when making a selection.

[064] The advantage of a VoIP call is that it is free of charge, but its disadvantage is [the occurrence of] shadow zones. The existence of shadow zones is due to the fact that establishing a VoIP call between terminal devices currently requires that the terminal devices have a connection to either a fixed network or a base station (access point) of a WLAN network. That is the reason why, VoIP calling is relatively rarely an option in mobile communication, however, in Figure 2B, it is available. [065] The advantage of GSM calling compared with VoIP calling is the wide operating range, since GSM networks covers a very wide geographic area. The disadvantage of GSM calling compared with VoIP calling is that it is fee-based.

[066] The advantage of video calling compared with VoIP and GSM calling is the added value associated with video images. The disadvantage of video calling is its high price and that rather few mobile phones currently in use have video-calling capability. Since menu 206 contains option 209 associated with video calling, the recipient's mobile phone contains video calling capability, i.e., it allows video calling.

[067] When the user has made a selection, the mobile phone calls the recipient's mobile phone according to this selection. [068] The invention relates to several embodiments.

[069] Figure 3 shows an embodiment of the invention, in which a communication connection between the originator's 302 terminal device 303 and the recipient's 304 terminal device 305 is established in the telecommunication network 301.

[070] The telecommunication network 301 contains at least one trunk network and one access network. It is also possible for the trunk and access networks to be one and the same. The originator's terminal device 303 is connected with the same type of access network, or a different type of access network than is the case with the recipient's terminal device 305. [071] Generally speaking, several types of access networks are in existence. As examples of access network types may be mentioned GSM (Global System for Mobile communications) and WLAN (Wireless Local Area Network). The telecommunication network 301 advantageously supports the IP protocol.

[072] Telecommunication network 301 receives the connection-attribute query 306 initiated by originator 302. [073] Subsequently, the telecommunication network transmits a connection-attribute query to the connection attribute database 307, and obtains recipient's 304 connection attributes 309 from the connection attribute database 307 using the dataset 308 denoted by the connection- attribute query 306. [074] Each connection mode available to the recipient 304 determines at least one connection attribute. In other words, each connection mode that the initiator 302 may select on terminal device 303 determines at least one connection attribute included in the recipient's connection attributes 309. However, it should be mentioned that an individual connection mode is not necessarily determined based only on the recipient's 304 connection attributes 309.

[075] Moreover, connection attributes are associated with terminal device 303 belonging to originator 302, and influence the connection modes. [076] As an example may be mentioned situation, in which the maximum connection speed of 128 kbit/s is associated with recipient's terminal device 305, and a maximum connection speed of 64 kbit/s is associated the originator's terminal device 303. Thus, the maximum connection speed of each possible [available] connection mode is 64 kbit/s. [077] The dataset 308 denoted by connection-attribute query 306 may contain the recipient's E.164 number, which is used as a search key in the search related to connection attribute database 307. In addition, or alternatively, dataset 308 may contain at least one of the following data elements: a) The address for connection attribute database 307, b) the recipient's E.164 number, to which a prefix is added due to the intelligent network server, or c) connection data associated with another recipient.

[078] The connection modes related to the invention advantageously include at least one of the following connection modes: Calling an E.164 number, VoIP calling, a data connection, a video connection, electronic mail, fax, and instant messaging.

[079] In several embodiments of the invention, telecommunication network

301 transmits the connection attributes 309 obtained from database 307 to the originator's terminal device 303.. Subsequently, telecommunication network 301 receives the connection mode related to selection 310 sent from originator's terminal device 303, and creates a communication connection

311 according to selection 310 between originator's 302 terminal device 303 and recipient's 304 terminal device 305. [080] Figure 3 thus shows two terminal devices. Communication connection 311 may also be created between more than two terminal devices, depending on the connection mode. As an example may be mentioned a group call.

[081] Typical of the invention is that communication connection 311 to the recipient's 304 terminal device 305 is established through at least two different connection modes.

[082] In addition to terminal device 305, recipient 304 may have at least one other terminal device. This allows for reaching the recipient 304 through at least two different communication terminal devices. [083] Figure 4A shows a method for creating a communication connection in a communication network between an originator's terminal device and a recipient's terminal device, i.e., between the terminal devices in their possession.

[084] The method implements the embodiment of the invention shown in Figure 3, and as mentioned later, the embodiments of the invention shown in

Figures 5A - 5C.

[085] The method comprises the following steps to be executed in a telecommunication network:

The connection-attribute query initiated by the originator is received 401 ;

The connection-attribute query is transmitted 402 to the connection attribute database; The connection attributes from the connection attribute database associated with the recipient are obtained 403 using the dataset denoted by the connection-attribute query, whereby the connection attributes contain at least one of the following connection attributes related to the terminal device: Type of access network, connection speed, QoS class, connection fee, terminal device capability set, communication application data;

The connection attributes are transmitted 404 to the originator's terminal device;

The selection sent from the originator's terminal device are received 405, wherein the selection relates to the connection modes determined by the connection attributes, and the communication connection between the originator's and the recipient's terminal device according to the selection is established 406. [086] In one embodiment of the invention, the connection-attribute query 306 mentioned in step 401 is sent from terminal device 303 belonging to originator 302. Thus originator 302 or terminal device 303 needs to know where to send connection-attribute query 306.

[087] The method therefore comprises at least six steps 401-406. Additional steps may be added to the method, if required. [088] Figure 4B shows the additional steps related to the ENUM query, which are executed, if required, before step 401 of the method. In other words, the additional steps are executed before the connection attribute query 306 initiated by originator 302. The details of the ENUM query are shown above in Figure 1. [089] The method comprises these steps:

The ENUM query sent from the originator's terminal device related to the recipient's connection data is received 407;

The ENUM query is transmitted 408 to the ENUM database; and

The recipient's connection data in response to the ENUM query is obtained 409 from the ENUM database.

[090] More specifically, the recipient's connection data is obtained from the ENUM database in step 409 combined or in several NAPTR records. Dataset 308 denoted by the connection attribute query 306 shown in Figure 3 advantageously contains the recipient's data element obtained in step 409. This data element therefore comes from the NAPTR record read from the ENUM database. [091] The data element contains some of the connection data associated with the recipient and that were used in step 403. Thus, by using the data element, the recipient's connection attributes are obtained from connection attribute database in step 403. [092] Figure 4C shows two additional steps for creating the connection- attribute query and that are interchangeable. [093] The method comprises this step:

The recipient's connection data are transmitted 410 to the terminal device belonging to the originator in order to create the connection-attribute query.

[094] Hence, step 410 is needed when terminal device 303 creates connection query 306.

[095] Alternatively, the method comprises this step:

A connection-attribute query is created 411 in the communication network.

[096] Instead of terminal device 303 in step 411 , some other network element coupled with communication network 301 creates connection- attribute query 306.. As examples of such a network elements may be mentioned an intelligent network server and an IMS (IP Multimedia Subsystem) server.

[097] Both steps 410 and 411 are executed after step 409, and before step

401.

[098] Figure 4D shows the additional steps for updating the connection attribute database; Updating of the connection attribute database has to do with the fact that by carefully keeping a database current, accessing data from the database becomes more practical.

[099] Updating of the connection attribute database also has to do with the fact that by carefully keeping a database current, updating the database will burden the telecommunication network less. In practice, it is likely impossible that terminal devices on the World Wide Web will be sending their connection attributes to a connection attribute database at, say, one-minute intervals. If the terminal devices would be sending their communication attributes at one- minute intervals, the connection attribute database would not be a real-time database, strictly speaking. [0100] In order to reduce the stress on the communication network, updating of the connection attribute database should be done ad-hoc. [0101] For ad-hoc updating, the method comprises the following steps executed in response to a connection attribute query: a connection update request is sent 412 to the recipient's terminal device, and in response to this connection update request the updating related to the recipient's connection attributes is received 413, and the update is transmitted 414 to the connection attribute database. [0102] Since steps 412 - 414 are executed in response to the connection- attribute query, they are executed after step 401 , but before step 403. [0103] When executing steps 412 - 414, the recipient's connection attributes just updated in step 403 are obtained from the connection attribute database. Therefore, the connection modes shown by originator's 302 terminal device 303 are real, i.e., both terminal device 303 and terminal device 305 support the shown connection modes. [0104] Figure 4E shows a method for a second embodiment. Figure 3 shows that connection attributes 309 are transmitted to originator's 302 terminal device 303. Alternatively, connection attributes 309 may be transmitted to a network element that executes connection-mode determination on behalf of terminal device 303. It is therefore assumed that the network element is also using the connection attributes of the originator's terminal device 303.

[0105] The second embodiment of the invention differs from the embodiment shown in Figure 4A, in that step 404 is omitted. [0106] In the second embodiment of the invention, the same steps 401 - 403 as in Figure 4A are executed. After step 403, the following occurs in the communication network: connection attributes 415 are transmitted to the network element, and the connection mode data determined on the basis of the connection attributes is transmitted 416 from the network element to the terminal device. [0107] The terminal device is a terminal device belonging to the originator. Connection mode data are data based on which, the terminal device is able to show the connection modes to its user or the originator. [0108] After step 416, in the second embodiment of the invention, the same steps 405 and 406 as in Figure 4A are executed. [0109] The following figures 5A - 5C illustrate the steps of the method shown in Figures 4A - 4C. [0110] As for the selection 310 related to the connection mode and the creation of communication connection 311 , the embodiments are the same as in Figure 3, which is why selection 310, communication connection 311 , recipient 304, and terminal device 305 used by the recipient are omitted from Figures 5A - 5D.

[0111] Figure 5A shows an embodiment of the invention, in which the ENUM query is executed and connection-attribute query 306 comes from originator's 302 terminal device 303. [0112] First, the terminal device 303 belonging to the originator 302 sends an ENUM query 502 to the ENUM-database server 501. In response to the ENUM query 502, the ENUM-database server 501 retrieves the recipient's connection data and sends them to the originator's 302 terminal device 303. The use of the ENUM-database server 501 thus matches the use of server 105 shown in Figure 1. [0113] The recipient's connection data sent by ENUM-database server 501 contain one or more NAPTR records. Some of the NAPTR records contain the Internet address of connection attribute database 307. [0114] Subsequently, terminal device 303 creates connection-attribute query 306 and sends it to the Internet address of the connection attribute database 307 obtained from the ENUM-database server 501.

[0115] In other words, the method steps 407-410 shown in Figures 4B and 4C are executed in Figure 5A.

[0116] When connection attributes 309 are retrieved from connection attribute database 307, they are delivered to terminal device 303. The connection attributes 309 are omitted in Figure 5A.

[0117] Figure 5B shows an embodiment of the invention, in which the connection-attribute query 506 comes from an intelligent network server 503. The intelligent network server 503 may be used in the method according to the invention, e.g., in the following way. [0118] The originator 302 keys on terminal device 303 the prefix preceding the E-164 number of the recipient's terminal device.

[0119] The originator then makes a call 504 to the recipient's E.164 number, to which a prefix is added. Due to the prefix, the call 504 is directed to the intelligent network server 503 in communication network 301. [0120] In response to the call 504, the intelligent network server 503 creates a connection-attribute query 306 and sends it to the connection attribute database 307. [0121] The use of the intelligent network server 503 or an IMS subsystem is one alternative in terms of executing method step 411 shown in Figure 4C. [0122] When connection attributes 309 are retrieved from connection attribute database 307, they can be delivered to terminal device 303, either directly or through intelligent network server 503. The connection attributes 309 are omitted in Figure 5B.

[0123] Figure 5C shows an embodiment of the invention, in which the connection-attribute query 306 originates from a server providing push- service, indicated more briefly as intelligent network server 503. [0124] The push server 503 sends connection-attribute query 306 to the connection attribute database 307 through communication network 301. In response to the connection-attribute query 306, the push server 503 obtains the connection attributes 309 read from the connection attribute database 307. [0125] Push server 503 then transmits its acquired connection attributes 309 to terminal device 303 through communication network 301. [0126] The use of the push server 503 is another alternative in terms or executing method step 411 shown in Figure 4C. [0127] Figure 5D shows an embodiment of the invention, in which the server containing the connection attribute database 307 is a push server 503. The embodiments described above assume that connection attribute database 307 is situated on a server, whereby the connection is obtained through communication network 301. [0128] Figure 5D assumes that connection attribute database 307 is situated on a push server 503.

[0129] It may be presumed that originator 302 is given permission on the push server 503 to send connection attributes. In this way, push server 503 sends connection attributes 309 to originator's 302 terminal device 303 through communication network 301 according to the permission given by the originator 302.

[0130] The connection-attribute query 306 associated with connection attributes 309 gives rise to, e.g., the following situations inside the push server 503: terminal device 305 has logged into telecommunication network 301 , terminal device 305 has logged out of telecommunication network 301 , a communication application is installed in terminal device 305, [and] the communication application is removed from the terminal device 305. [0131] The above-mentioned situations affect the connection modes, with which terminal device 305 belonging to recipient 304 and terminal device 303 belonging to originator may communicate with one another. [0132] It is conceivable that the push server generates the connection- attribute query so that the originator 302 obtains in his terminal device 303 the connection attributes 309 updated by the recipient 304, as soon as the recipient's terminal device encounters any of the above-mentioned situations affecting the connection modes. For the originator to obtain in his terminal device 303 the connection attributes 309 updated by the recipient 304, the originator should announce to the push server 503 that recipient's 304 connection attributes are of interest to him. In the same announcement, the originator may signal his interest in one or more of the recipient's other connection attributes. [0133] If the communication network 301 contains several access networks, the terminal device 305 may be simultaneously logged into at least two access networks. If terminal device 305 is simultaneously logged in to, e.g., the GSM network and the WLAN network, the originator 302 may acquire the connection for terminal device 305 on his terminal device 303 through either access network. [0134] In addition to connection attributes 309, push server 503 may transmit other data, such as the recipient's status data. However, it is essential for the invention that push server 503 will transmit at least the connection attribute data. As with the status service, with the service provided by the push server 503, the user groups also need to be determined in order for connection attribute data to be transmitted between each member of the user group. For instance, family members may constitute a group, whereby connection attributes are transmitted between family members. Likewise, the members of a work team may form their own group. [0135] Figure 6 shows a connection attribute database. Database 601 is intended to manually improve the recipient's accessibility from the telecommunication network 602 terminal device 603 belonging to the originator, Improving the recipient's accessibility means that the other user (the originator) of the communication network 602 may test the connection modes and possibly select one among them. [0136] Database 601 contains the connection attribute data 604 associated with users of the terminal devices, while including the connection attributes 605 associated with the recipient in the connection attribute data 604. [0137] The connection attribute data 604 are arranged such that in response to the connection-attribute query 606 related to the recipient, the connection attributes 605 are obtained from database 601.

[0138] The connection attributes 605 contain at least one of the following connection attributes related to the terminal device associated with the recipient: Type of access network, connection speed, QoS class, connection fee, terminal device capability set, communication application data. [0139] Moreover, database 601 is in connection with telecommunication network 602 such that the connection attributes 605 are transferable through telecommunication network 602 to the terminal device 603 belonging to the originator.

[0140] In the following, connection attributes 605 are described in more detail. The connection attributes are thus terminal-device-related data such that certain connection attributes associate the recipient with each terminal device.

[0141] Some terminal devices are able to use more than one access network simultaneously. Moreover, some terminal devices are able to use more than one connection simultaneously, or more than one communication application simultaneously. As a result, connection attributes are terminal- device-related, access-network-related, connection-related and/or communication-application-related data.

[0142] The access network type may be a GSM network, another mobile- phone network, a WLAN, or another access network. When both recipient's and originator's access network is of the WLAN type, a free-of-charge connection is usually possible. This is one reason for recording the access network type used by the recipient in database 601. Moreover, the connection speed pertaining to the connection attributes, QoS class and connection fee depend at least partly on the type of network, or more specifically, the capabilities of the access network. [0143] The connection speed included in the connection attributes may represent the connection speed to be created. The connection speed contains at least one of the following data: Minimum speed, maximum speed, or remaining capacity, when part of the recipient's terminal-device data- transfer capacity is still in use. The minimum speed indicates, which data transfer speed is required as a minimum by the recipient's terminal device. The maximum speed indicates, which data transfer speed the recipient's terminal device is capable of as a maximum. [0144] The QoS (Quality of Service) class included in the connection attributes may represent the quality of the connection. The QoS class indicates at least one of the following data: Access-network QoS class, terminal-device QoS class, terminal-device connection-related or communication-application-related QoS class. All the aforementioned QoS classes may be included in the QoS class stored in the connection attribute database. Alternatively, the QoS class stored in the connection attribute database contains the weakest of these class sets: Access-network QoS class, terminal-device QoS class, or terminal-device connection-related or communication-application-related QoS class.

[0145] The connection fee is most easily communicated, when the connection is free of charge, or when the connection is at a fixed rate. When the connection is at a fixed rate, a local call charge may, for instance, be added to the final charge. [0146] The terminal device capability set represents the terminal device technical capabilities, such as: Display resolution, processor power, memory capacity, keyboard and optional equipment. The keyboard may be mechanical or a keyboard based on a touch-sensitive surface. The most common keyboard types are a QWERTY keyboard and a numeric keypad. As optional equipment for the terminal device may be mentioned, for example, a camera, a headset, a mouse, and a joystick. The camera may be a video camera or a camera capturing still frames. Moreover, the terminal device capability set advantageously contains data from the terminal-device operating system. [0147] As the last connection attribute, we describe the communication application data. A communication application means an application capable of communicating over the communication network along with a second network element. The communication application data indicate the type of the communication application and/or identifier data (name and version number) of the communication application. It is possible to install several communication applications on the terminal device and whose data are included in the communication application data.

[0148] Database 601 may contain a user interface, through which users are able to update their connection attributes, however, updating of the database is advantageously automated such that the users' terminal devices send the updates related to the connection attribute data to the database without any user intervention. Furthermore, or alternatively, one or more additional network elements besides the terminal device send connection-attribute-data updates to the database.

[0149] The updating of database 601 is advantageously done by using the network element of the access network. The network element senses, when a terminal device is logging into the communication network through the access network. Likewise, the network element senses, when a terminal device is logging out of the communication network. In these situations, the network element updates the terminal-device connection attributes to the connection attribute database 601. Connection attributes to be updated are especially: type of access network, maximum connection speed, and QoS class.

[0150] When comparing Figures 6 and 3, it can be seen that database 601 represents the connection attribute database 307 shown in Figure 3, and communication network 602 represents the communication network 301 shown in Figure 3.

[0151] In terms of operating database 601 , the origin of the connection- attribute query 606 is irrelevant, per se. Generally speaking, it is sent from the terminal device belonging to the originator, or from some other terminal device, an intelligent server, an IMS subsystem server, a server offering push service, or a network element communicated through another communication network 602.

[0152] Database 601 may be in use only by one network operator or server operator. If an operator is active only in one country, the whole database 601 is advantageously installed on one server. [0153] If an operator is active in several countries, or the database 601 uses at least two operators, the database 601 should probably be distributed [decentralized]. The database may be distributed such that one server is installed for each country, or such that each operator manages one server, in which the operator's own client connection attribute data are located. [0154] The embodiments shown in Figures 4B and 5A are especially suitable for a situation, in which database 601 is distributed. [0155] Alternatively, database 601 may be distributed in terms of different types of connection attribute data on two or more sections. [0156] The following connection attribute data are dynamic data relative to the mobile terminal device: Access network type, connection speed, and QoS class. More specifically, when the recipient's terminal device 305 is a mobile terminal device, the above-mentioned connection attribute data will need to be updated fairly often to the connection attribute database. [0157] The following connection attribute data are naturally static: Terminal device capability set and communication application data. Static data need not be updated nearly as often as dynamic data. Database 601 may be distributed such that dynamic and static data are located in their own separate sections.

[0158] Generally speaking, processing the distributed database section may be different. As an example, we mention a situation, in which the database 601 unit containing the dynamic connection attribute data is updated through the agency of the access network elements, and the database 601 unit containing the static connection attribute data is updated through the agency of the operators such that an Internet user interface to database 601 is created for the users. [0159] No database 601 distribution method or combination of distribution methods should be excluded.

[0160] Updating the database 601 is therefore done by arranging an Internet user interface. The Internet user interface is, for example, such that the user selects from a menu the manufacturer of his first terminal device, whereupon a new menu containing the terminal device models of the manufacturer opens to the user. Especially in the case of mobile phones, the terminal- device model accurately states the terminal device capability set included in the connection attributes 605. [0161] Each GSM and UMTS (Universal Mobile Telecommunications System) mobile phone has an individual IMEI (International Mobile Equipment Identity) code. The IMEI code contains data blocks, whereby one data block designates the mobile-phone model, and another data block designates the version number of the mobile-phone software. As a result, the terminal device capability set included in the connection attributes 605 based on the IMEI code is quite easily and reliably determined.

[0162] Updating the database 601 is thus done by arranging the IMEI code as follows: When the mobile phone of the GSM or GPRS (General Packet Radio Service) network executes a location update, the mobile phone sends its own IMEI code either to the MSC or SGSN element. [0163] Because the mobile-phone model is inferable from the IMEI code and the model determines the terminal device capability set, this terminal device capability set included in a certain E.164 number may be stored in the database 601 through the agency of the access network (GSM or GPRS). This updating mode of the database therefore does not require any user action.

[0164] An MAC address is an address used on Ethernet networks, which address identifies the terminal device. It is used, for example, on WLAN networks. An MAC address may be used as a search key, when the "access-network type" included in the connection attributes 605 is updated as a result of logging into or out of the communication network. The MAC address is especially necessary when the terminal-device E.164 number is not transmitted to an access network element.

[0165] In order to read and update the connection attributes 605 stored in the database 601 , the connection attributes 605 advantageously contain an E.164 number, and moreover, the connection attributes 605 advantageously contain at least another IMEI-code or MAC-address data. [0166] Furthermore, the connection attributes 605 may contain at least one mailing address.

[0167] The mailing address contained in the connection attributes 605 are, e.g., the recipient's home address, vacation home address, or the workplace address. When the originator sees the mailing address of the recipient on the display of the terminal device being used, a mail may be sent to the recipient. [0168] The use of connection attributes 605, in addition to the creation of the communication connection, affects how the connection attributes 605 and connection modes are displayed. The user may thus view the telephone numbers associated with the connection modes, other network addresses, or e-mail addresses. Partly for this reason, the database 601 may be compatible with the use of connection data servers based on known text- messaging services.

[0169] In addition, in one embodiment of the invention, the originator may send an e-letter (electronic letter) to the recipient. For example, the Finnish postal service offers an e-letter service. When using this e-letter service, the originator sends a letter in a certain file format to an Internet address of a server offering e-letter service. The letter sent by the originator via the server is then printed out on paper and placed in an envelope, and then delivered to the recipient via the postal service. This embodiment of the invention is suitable for mailing to a recipient not only letters, but also, for example, postcards and invoices. [0170] Figure 7 shows a terminal device using connection attributes. The connection attributes may be assumed to be coming from the connection attribute database. Terminal device 701 contains at least display 702, telecommunication means 703, and means for handling connection attributes 704.

[0171] Terminal device 701 is adapted to receive connection attributes sent through a telecommunication network 705 by telecommunication means 703, when the connection attributes contain at least one of the following connection attributes related to a terminal device: Type of access network, connection speed, QoS class, connection fee, terminal device capability set, communication application data; determine via the connection-attribute-processing means 704 the connection modes of the received connection attributes 706, with which the recipient associated with the connection attributes may be reached; create user-interface elements for the connection modes via the connection-attribute-processing means 704; show user-interface elements on display 702; receive in the connection-attribute-processing means 704 the terminal-device 701 user selection associated with the user-interface elements; and execute the procedure according to the selection of the terminal- device 701 user. [0172] The communication means 703 assembly especially depends on the intended use of terminal device 701. If the terminal device is a desktop computer, the telecommunication means 703 contain, e.g., a modem or ADSL (Asymmetric Digital Subscriber Line) adapter. If terminal device 701 is a mobile phone, the telecommunication means 703 contain at least one radio unit. Alternatively, terminal device 701 may be a supported computer or PDA.

[0173] The telecommunication means 703 may contain, e.g., a GSM radio unit and a WLAN radio unit. Generally speaking, terminal device 701 is able to communicate via telecommunication means 703 in telecommunication network 704 through at least one access network. [0174] Especially the size of display 702 affects how the user-interface elements are shown to the terminal device 701 user. Windows, icons, menus and options are typical user-interface elements. Icons and options should be sufficiently large, so that the user is able to use them, i.e., to select the connection mode.

[0175] Figures 2A and 2B show the user-interface elements created by the connection-attribute-processing means 704 and the connection modes associated therewith, which connection-attribute-processing means 704 are determined based on the received connection attributes 706.

[0176] In the following, we show an example related to Figure 2A and the operation of connection-attribute-processing means 704.

[0177] It is assumed that the recipient is using the communication application named "Messenger," whose version number is 3.4. In other words, the communication application identifier data are "Messenger 3.4."

[0178] It is assumed that in terminal device 701 is installed the newer version of the same communication application, "Messenger 4.1", which supports all "Messenger 3.4" application capabilities. [0179] It is, furthermore, assumed that "Messenger 3.4" does not support all "Messenger 4.1 "-application capabilities.

[0180] In this way, connection-attribute-processing means 704 determines the "Messenger 3.4"-connection attribute associated with the recipient and the "Messenger 4.1 "-connection attribute associated with terminal device 701 , provided such a connection mode is possible, whereby the "Messenger

4.1" application operates in "Messenger 3.4" mode. As a result, the connection-attribute-processing means create icon 204 for window 201 containing text "Messenger 3.4."

[0181] In addition, connection-attribute-processing means create the icon for window 205, whereby the text contained therein - "Messenger 4.1" - is italicized, as the relevant connection format is not available between terminal device 701 and the terminal used by the recipient.

[0182] Moreover, the operation of terminal device 701 is shown in Figure 3, since terminal device 701 represents terminal device 303 belonging to the originator shown in Figure 3, and communication network 705 represents communication network 301 shown in Figure 3.

[0183] As mentioned above, terminal device 701 is adapted to execute the procedure according to the user selection. This procedure is preferably one of the following procedures: Showing on the display the connection attributes associated with the selected user-interface element, creating a communication connection to a certain recipient terminal device via the telecommunication network, sending an e-letter (electronic letter) to the recipient.

[0184] Two embodiments are related to the invention concerning the reception of the connection attributes 706. [0185] In the first embodiment, the terminal device 701 is adapted to receive connection attributes 706 in response to the connection-attribute query initiated by the terminal device. The terminal device may send the connection-attribute query directly to the server, where the connection attribute database is stored. Hence, terminal device 701 , or its user, must know the Internet address of the server.

[0186] Figures 5A - 5C show other alternatives for how the user of terminal device 701 may initiate a connection-attribute query. Terminal device 701 represents terminal device 303 shown in Figures 5A - 5C. [0187] In the second embodiment, connection attributes 706 are sent from a push service. Figure 5D shows the push-service operation. Terminal device 701 represents terminal device 303 shown in Figures 5D. [0188] Terminal device 701 is advantageously adapted to send via the telecommunication means its own connection attributes to the connection attribute database, the connection modes determining their own connection attributes, with which the terminal device user may be reached. The connection attribute database is omitted in Figure 7.

[0189] When terminal device 701 is able to send its own connection attributes to the connection attribute database, then it is easier than previously for other users of other terminal devices to reach the terminal- device 701 user.

[0190] Terminal device 701 is advantageously adapted to send its own connection attributes in at least one of the following situations: The terminal device has logged into a telecommunication network, the terminal device has logged out of a telecommunication network, a communication application is installed in the terminal device, [and] the communication application is removed from the terminal device.

[0191] Figure 8 shows a network element using connection attributes. The connection attributes may be assumed to be coming from the connection attribute database. Network element 801 contains at least telecommunication means 802, and means for processing connection attributes 803. [0192] Network element 801 is adapted to receive connection attributes 805 sent through a telecommunication network 804 by telecommunication means 802, whereby the connection attributes contain at least one of the following connection attributes related to the terminal device: Type of access network, maximum connection speed, QoS class, communication application type, or communication-application identifier data, determine from the connection attributes 805 received via connection-attribute-processing means 803 the connection mode data 806, with which the recipient associated with the connection attributes may be reached; and transmit the connection mode data 806 to the terminal device 807 belonging to the originator.

[0193] Terminal device 807 may be assumed to contain means in order to create user-interface elements related to connection mode data 806. When terminal device 807 shows the user-interface elements on its display, the originator may select the most interesting connection mode among them. [0194] Terminal device 807 therefore contains, in addition to connection- attribute-processing means 704 of terminal device 701 shown in Figure 7, or instead thereof, the above-mentioned means in order to create the user- interface elements related to connection mode data 806.

[0195] The capabilities of the following network element are optional:.

Network element 801 is adapted to receive via telecommunication network means 802 the connection attributes 808 related to terminal device 807 and sent from terminal device 807. Network element 801 is adapted to send via telecommunication means 802 the connection attributes 808 related to terminal device 807 through telecommunication network 804 to a connection attribute database, such as database 601 shown in Figure 6.

The connection attributes 808 sent by network element 801 do not necessarily come from terminal device 807, instead network element 801 has determined connection attributes 808 related to terminal device 807.

Network element 801 is advantageously a network element of the access network. Thus, network element 801 communicates with terminal device 807, when the terminal device is logged into the access network through the latter, or when the terminal device is logged out from the access network through the latter. [0196] Besides the embodiments, descriptions and examples of the invention presented above, the connection attribute database, and terminal device, the implementation of the method according to the invention may be done in alternative ways, which are, however, obvious to a specialist in the field [person skilled in the art] on account of his expertise and the suggestions provided by the patent application.

Claims

1. A method for creating a communication connection between an originator's terminal device and a recipient's terminal device in a telecommunication network, c h a ra cte ri ze d in that the method comprises the steps to be executed in a telecommunication network, whereby a connection-attribute query initiated by the originator is received (401), the connection-attribute query is transmitted (402) to a connection attribute database, connection attributes from the connection attribute database associated with the recipient are obtained (403) by using the dataset denoted by the connection-attribute query, whereby the connection attributes contain at least one of the following connection attributes related to the terminal device: the type of access network, speed of the connection, QoS (Quality of Service) class, charge for the connection, terminal device capability set, communication application data; the connection attributes are transmitted (404) to the originator's terminal device, the selection sent from the originator's terminal device is received

(405), wherein the selection relates to the connection modes defined by the connection attributes, and and the communication connection between the originator's terminal device and the recipient's terminal device according to the selection is established (406).

2. A method according to claim 1 , c h a ra cte ri ze d in that the method, furthermore, comprises steps executed in response to a connection- attribute query: a connection update request is sent (412) to the recipient's terminal device and in response to the connection update request an update related to the connection attributes is received (413), and the update is transmitted (412) to the connection attribute database.

3. A method according to claim 1 , c h a ra cte ri ze d in that the communication modes contain at least one of the following connection modes: Calling an E.164 number, VoIP (voice over internet protocol) calling, a data connection, a video connection, electronic mail, fax, and instant messaging.

4. A database according to claim 1, characterized in that the communication connection to the recipient's terminal device is created by at least two different connection modes.

5. A database according to claim 1, characterized in that the recipient may be reached by at least two different terminal devices.

6. A method according to claim 1, characterized in that the dataset denoted by the connection-attribute query contains at least one of the following data elements: the address for the connection attribute database, the recipient's E.164 number, the recipient's E.164 number added with a prefix, [and] other connection data associated with the recipient.

7. A method according to claim 1, characterized in that the method, furthermore, comprises the following steps being executed before the connection-attribute query initiated by originator: the ENUM (tElephone NUmber Mapping) query sent from the originator's terminal device related to the connection data is received (407), the ENUM query is transmitted (408) to the ENUM database; and the recipient's connection data in response to the ENUM query is obtained (409) from the ENUM database.

8. A method according to claim 7, characterized in that the dataset denoted by the connection-attribute query contains at least one of the data elements included in the recipient's connection data obtained from the ENUM database.

9. A method according to claims 7 and 8, characterized in that the method, furthermore, comprises the step: the recipient's connection data are transmitted (410) to the originator's terminal device in order to create the connection-attribute query.

10. A method according to claims 7 and 8, characterized in that the method, furthermore, contains the step: a connection-attribute query is created (411) in the telecommunication network.

11. A database (601 ) for manually improving a recipient's accessibility from a telecommunication network (602) terminal device belonging to an originator, cha racte rized in that the database (601) contains connection attribute data (604) associated with users of the telecommunication network (602) terminal devices, the connection attribute data including connection attributes (605) of the recipient, the connection attributes (604) being arranged such that in response to a connection-attribute query (606)related to the recipient, the connection attributes (605) associated with the recipient are obtained from the database

(601 ), whereby the connection attributes (605) include at least one of the following connection attributes related to the terminal device: the type of access network, speed of the connection, QoS (Quality of Service) class, connection fee, terminal device capability set, communication application data, and the database (601 ) being in connection with the telecommunication network (602) such that the connection attributes (605) are transferable through the telecommunication network (602) to the terminal device (603)belonging to the originator.

12. A database according to claim 11 , c h a ra cte ri ze d in that each connection mode, with which the recipient may be reached, determines at least one connection attribute.

13. A database according to claim 11 , c h a racte ri ze d in that a connection-attribute query is sent from a terminal device, intelligent-network server, IMS (IP multimedia subsystem) subsystem server, a server providing a push service, or a network element communicating through another telecommunication network.

14. A database according to claim 11 , c h a ra cte ri ze d in that the connection attributes (605) contain at least one mailing address:

15. A database according to claim 11 , c h a ra cte ri ze d in that the database (601) is distributed.

16. A terminal device (701 ) containing at least a display (702) and telecommunication network means (703), c h a racte ri ze d in that the terminal device (701) furthermore contains means for processing connection attributes (704), and the terminal device (701 ) is adapted to receive with telecommunication means (703) the connection attributes (706) sent through a telecommunication network (705), whereby the connection attributes (706) contain at least one of the following connection attributes related to a terminal device: the type of access network, speed of the connection, QoS (Quality of Service) class, connection fee, terminal device capability set, communication application data; determine with the means for processing connection attributes (704) the connection modes of the received connection attributes (706), with which the recipient associated with the connection attributes is reachable; create user-interface elements for the connection modes with the means for processing connection attributes (704); show user-interface elements on a display (702); receive in the means for processing connection attributes(704) the terminal-device (701) user selection associated with the user-interface elements, and execute the procedure according to the selection of the user of the terminal device (701 ).

17. A terminal device according to claim 16, c h a ra cte ri ze d in that the procedure is one of the following: showing on the display the connection attributes associated with the selected user-interface element, creating a communication connection to a certain recipient terminal device through the telecommunication network, sending an e-letter (electronic letter) to the recipient.

18. A terminal device according to claim 16, c h a ra cte ri ze d in that the terminal device (701 ) is adapted to receive connection attributes (706) in response to the connection-attribute query initiated by the terminal device (701 ).

19. A terminal device according to claim 16, c h a ra cte ri ze d in that that the connection attributes are sent from a push service (706).

20. A terminal device according to claim 16, c h a ra cte ri ze d in that that the terminal device, furthermore, is adapted to send via the telecommunication means (703) its own connection attributes to the connection attribute database, said own connection attributes determining the connection modes, with which the user of the terminal device (701) is reacahable.

21. A terminal device according to claim 20, c h a ra cte ri ze d in that the terminal device (701 ) is adapted to send its own connection attributes in at least one of the following situations: the terminal device has logged into a telecommunication network, the terminal device has logged out of a telecommunication network, a communication application is installed in the terminal device, the communication application is removed from the terminal device.

22. A network element (801) containing at least telecommunication means (802), c h a ra cte rized in that the network element (801), furthermore, contains means for processing connection attributes (803), and the network element (801) is adapted to receive connection attributes (805) sent through a telecommunication network (804) by telecommunication means (802), whereby the connection attributes (805) contain at least one of the following connection attributes related to a terminal device: the type of access network, speed of the connection, QoS (Quality of Service) class, connection fee, terminal device capability set, communication application data; determine from the connection attributes received by the means for processing connection attributes (803) the connection-mode data (806), with which the recipient associated with the connection attributes may be reached, and transmit the connection-mode data (806) to the terminal device belonging to the originator.

23. A network element according to claim 22, c h a ra cte ri ze d in that the network element is adapted to receive the connection attributes (808) related to the terminal device and sent from the terminal device (807) via the telecommunication means (802) .

24. A network element according to claim 22, c h a ra cte ri ze d in that the network element is adapted to send to the connection attribute database (601 ) the connection attributes related to the terminal device (807) via the telecommunication means (802) through the telecommunication network (804).