Dynamic selection by a caller from a multitude of devices of a called party

DE602015090499T2Active Publication Date: 2024-11-27ORANGE SA
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
DE602015090499
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Priority Date
2014-06-23
Filing Date
2015-06-11
Publication Date
2024-11-27
Estimated Expiration
2035-06-11

AI Technical Summary

Technical Problem

Current IP networks lack an efficient method for a caller to select the most capable terminal among multiple connected devices of a second user to provide the desired service, as existing solutions either aggregate terminal capacities inaccurately or impose significant delays in obtaining necessary information.

Method used

A method where a first user independently receives requests from each client device of a second user, selects the most capable terminal based on received technical capacity information, and establishes a session with that terminal, allowing for quick identification and selection of the optimal device for service provision.

Benefits of technology

Enables the first user to quickly and accurately choose the most suitable terminal for establishing a session, ensuring the desired service quality is met, whether the second user has multiple connected devices or not, by obtaining technical capabilities before attempting a session.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The present invention relates to IP type communications networks (“ Internet Protocol "), and in particular those among the IP networks which are capable of implementing advanced session control protocols. IP networks allow the broadcasting of conversational data, within the framework of services such as "Voice over IP" (VoIP), "Content Sharing", or "Instant Messaging".

[0002] More particularly, the present invention relates to the means implemented in an IP network to enable the sender of a request to obtain the technical capabilities of the client devices of the recipient of the request connected to said IP network, so as to be able to select, from among these client devices, the one which appears most capable of satisfying this request.

[0003] These “client devices” can be, for example, a fixed or mobile terminal, or a home gateway (“ Residential Gateway » in English) is located in a company. For the sake of brevity, the generic term "user terminal", or simply "terminal", will frequently be used below to designate these various pieces of equipment.

[0004] IP network communication services can identify physical or virtual resources using character strings such as a "URI" (initials of the English words " Uniform Resource Identifier » meaning "Uniform Resource Identifier"). The syntax of URIs is defined in the IETF RFC 3986 document; knowing the URI of a resource makes it possible to obtain the IP address of a device on the operator's network managing this resource. In this description, we will call "URI" any type of physical or virtual application resource identifier accessible on a network.

[0005] Classic advanced session control protocols, such as SIP (Simplified IP Protocol), Session Initiation Protocol » meaning "Session Initiation Protocol"), use so-called "signaling" messages, which are messages allowing a terminal to request a connection with another terminal, or also messages signaling that a telephone line is busy, or signaling that the called telephone is ringing, or signaling that such and such a telephone is connected to the network and can be contacted in such and such a way.

[0006] The SIP protocol was defined by the IETF ( Internet Engineering Task Force ) in RFC 3261. This protocol allows the establishment, modification and termination of multimedia sessions in a network using the IP protocol. The SIP protocol was subsequently extended, notably in RFC 3265. This extension defines event notification procedures.

[0007] The SIP protocol is used in particular in IMS type infrastructures (initials of the English words " IP Multimedia Subsystem » meaning “Multimedia Subsystem over IP”). IMS was defined by the 3GPP standards body (“ Third Génération Partnership Project ”) and TISPAN (“ Télécommunications and Internet Converged Services and Protocols for Advanced Networking ”) . It is a network architecture introduced by 3GPP for mobile networks, then adopted by TISPAN for fixed networks. This architecture allows the dynamic establishment and control of multimedia sessions between two clients as well as the reservation of resources at the level of the multimedia stream transport network. Thanks to this architecture, network operators can conveniently implement a management policy, provide a predetermined Quality of Service, and calculate the amounts to be billed to customers. IMS currently provides access to services such as telephony, videophony, Presence and Instant Messaging, for which it also manages the interaction.

[0008] Each user of an IMS network can be identified by means of various identities, including the IMPI (initials of the English words "IMPI"). IP Multimedia Private Identity » meaning “Private Identity for Multimedia IP”) and IMPU (initials of the English words “ IP Multimedia PUblic identity » meaning “Public Identity for Multimedia IP”).

[0009] The IMPI is defined in the 3GPP TS 23.228 specification. The IMPI is an identity permanently assigned by the network operator to a subscription with that operator, and is used, for example, for registration, access authorization, administration of services offered to the user, and billing (note that a user can have several IMPIs within the same subscription; each IMPI can thus be associated with a different client device). The IMPI has the form of a NAI (initials of the English words " Network Access Identifier » meaning “Network Access Identifier”), as defined in IETF RFC 4282.

[0010] A user uses their IMPU to communicate with other users. The IMPU is presented in the form of a URI or a short number, or any alias. For a given IMPU, there can be several IMPUs (often, a tel-URI and a SIP-URI). An IMPU can be shared with another phone, so that these phones can both be reached with the same identity (for example, a single phone number for an entire family of users). These identities are configured by the operator when a user creates an account with this operator, and used when registering a user's client device on the network.

[0011] When a user wishes to benefit from the services offered by an IMS network, he sends signaling messages to the network which may include various types of requests.

[0012] First, the user's client device must, with some exceptions (such as certain emergency calls), register with the network. When the network is unable to link this registration to a previous registration (for example, due to a network outage, or due to the client device being down for a period exceeding a predetermined value), the registration is considered an initial registration. After an initial registration, the user's client device must periodically send a request to the network to confirm that it wishes to maintain its registration.

[0013] To be able to register client devices, IMS networks include one or more registration servers, called "S-CSCF" (initials of the English words « Serving-Call Server Control Function » meaning “Waitress Call Session Control Function”), capable (among other functions) of managing the registration procedure of devices connected to the network.

[0014] IMS networks further include one or more query servers, called "I-CSCF" (initials of the English words " Interrogating-Call Server Control Function » meaning "Interrogating Call Session Control Function") - often physically combined with the S-CSCF registration servers to form call servers denoted "I / S-CSCF" - which, at the time of registration of a client device, interrogate a subscriber data server called "HSS" (initials of the English words " Home Subscriber Server» meaning "Home Subscriber Server"), in order to be able to select an S-CSCF server with the characteristics that are mandatory (and, where applicable, optional) required to achieve the level of service subscribed to by the user. HSS servers each contain a customer database, and are therefore the equivalent in IP networks of "HLR" servers (initials of the English words " Home Location Register » meaning « Home Location Register ») used in GSM networks. Each HSS server contains the « profile » of a certain number of client devices in the network, this profile including their registration status, authentication and location data, and the subscribed services.

[0015] In the process of creating a user account on an IMS network, the network operator first creates an IMS subscription in the HSS, which will serve as the basis for billing. The operator then notes, with reference to this subscription, the private IMPI and public IMPU identities of the users sharing this subscription, declares their service profiles and the IFCs (initials of the English words " Initial Filter Criteria » meaning Initial Filtering Criteria) associated, as well as many other user-related information.

[0016] IMS networks also include one or more servers called “P-CSCF” (initials of the English words “ Proxy-Call Server Control Function » meaning "Proxy Call Session Control Function"). For each client device connected to an IMS network, there is a P-CSCF server serving as a connecting entity between the IMS core network and the access network used by this client device; thus, all SIP signaling exchanged between the client device on the one hand, and the I-CSCF query server or the S-CSCF registration server on the other hand, passes through the P-CSCF server.

[0017] When a first user (called the "caller") sends a request to a second user (called the "called"), the caller does not (in general) know the capabilities of the called party's terminal, or the capabilities of the called party's terminals when the latter has several terminals (typically, each associated with a respective IMPI but with a single common IMPU). By "capabilities of a terminal", is meant, in the context of the present invention, the technical capacity of this terminal to participate in the provision of a particular service, for example a telephone service, or a High Definition (HD) Voice service, or a video service, or even an instant messaging service. However, knowledge of these technical capabilities would be very useful to the caller, because it would allow him to know: 1) whether one of the called party's terminals has sufficient capabilities for the service desired by the caller, and 2) if such a terminal exists, the identity of that terminal or how to contact it.

[0018] Various proposals are known in the state of the art to solve this problem.

[0019] In particular, we know of network solutions based on "application servers" that aggregate the capabilities of each of a user's connected terminals. However, these solutions do not reflect the capabilities of each of the connected terminals at a given time, because it is the aggregation of the capabilities of all the terminals that is presented, and not the individual capabilities of each terminal.

[0020] Other solutions, based on « forking » (i.e. transmission of a control signal to a plurality of recipient terminals), make it possible to explore the capabilities of at least some of the connected terminals, by sending them a dedicated request.

[0021] For example, application US 2011 / 314140 proposes a method for processing a SIP OPTIONS capability request message in an IMS network. A SIP proxy receives, from a requesting node, a SIP OPTIONS message intended for a user, called the called party, of the network (it is recalled that, according to the aforementioned RFC 3261 document, a SIP OPTIONS request allows a SIP agent to ask another SIP agent or a SIP proxy to provide it with its capabilities). The proxy sends the message to a plurality of devices of said called party, and receives a response (SIP 200 OK) from at least two of these devices. Each response received, which includes an identity of the responding device and an indication of the capabilities of the responding device, is stored in a memory. The proxy then prepares a response message containing the identities and capabilities of all the responding devices. Finally, this response message is sent to the requesting node (indeed, according to Sections 11.2 and 16.7 of RFC 3261, the proxy can only send one response to the requesting node).

[0022] This method according to application US 2011 / 314140 has the disadvantage that the procedure for aggregating and temporarily storing the responses requires means ad hoc in the proxy, and furthermore imposes a considerable delay on the requesting node before receiving the requested capabilities.

[0023] The section titled "Media Negotiation" of Mikka Poikselkâ et al.'s "IMS IP Multimedia Concepts and Services," March 17, 2009, John Wiley & Sons, describes the establishment of a normal session between two phones connected to an IMS network via GPRS technology.

[0024] Document US 2006 / 0218291 A1 describes a method for enabling end-to-end exchange of capabilities between two user client devices. This document highlights in particular that this exchange makes it possible to remedy the situation where several client devices of the same user share the same public identity (IMPU).

[0025] In summary, none of the known solutions allows a caller to efficiently select the called terminal most capable of correctly providing a service required by the caller.

[0026] The present invention therefore relates to a method according to claim 1.

[0027] Thus, according to the invention, each request sent by a client device of the second user reaches the first user independently of one another.

[0028] Thanks to these provisions, a first user can (for example when establishing a session) quickly obtain the capabilities of each of the terminals belonging to a certain second user and connected to the IP network.

[0029] According to particular characteristics, said method further comprises the following steps: c) after receiving said requests sent by client devices of the second user, the client device of the first user selects one of these client devices of the second user on the basis at least of the technical capability information contained in these requests, d) the client device of the first user sends, to the selected client device, a favorable response to the request sent during said step b) by this selected client device, and e) the client device of the first user and the selected client device enter into a session.

[0030] Thanks to these provisions, the first user can, on the basis of the capacity information received, select the second user's terminal most appropriate for providing a service desired by the first user.

[0031] According to even more specific characteristics: the request issued by each respective client device of the second user during said step b) includes a respective identifier of this client device, and the client device of the first user inserts the identifier of said selected client device in the response issued during said step d) to this selected client device.

[0032] Thanks to these provisions, the first user can know the technical capabilities of all the client devices of the second user currently connected to the IP network, even before attempting (possibly) to establish a session with this second user. If, for example, none of the second user's client devices suits him, the first user can decide not to attempt to establish a session with the second user.

[0033] According to other even more particular characteristics: said request issued by the client device of the first user during said step a) mentions a service that the first user wishes to obtain during the session being established, and during said step d), the client device of the first user issues an unfavorable response to the requests sent during said step b) by the client devices of the second user not selected.

[0034] Thanks to these provisions, the first user can, by means of the indicator according to the invention, quickly obtain the information necessary to be able to choose from among the client devices of the second user currently connected to the IP network, the optimal client device with which to establish a session. This embodiment is well suited to the case where the first user knows that the second user has several client devices currently connected to the IP network.

[0035] According to still other even more particular characteristics: prior to said step a), the client device of the first user sends, to said second user, a request mentioning a service that the first user wishes to obtain during the session being established, and during said step d), the client device of the first user sends an unfavorable response to the requests sent during said step b) by the unselected client devices of the second user.

[0036] Thanks to these provisions, a first request allows the first user to obtain a list of client devices belonging to the second user and capable of providing the desired service, then a second request allows the first user, by means of the indicator according to the invention or a request of a type dedicated to the invention, to obtain the information necessary to be able to choose the optimal client device from this list.

[0037] with whom to establish a session. This embodiment is well suited to the case where the first user is not sure in advance whether or not the second user has a plurality of client devices currently connected to the IP network.

[0038] According to still other even more particular characteristics, if no client device of the second user having issued during said step b) a request indicating its technical capabilities is technically capable of providing a service desired by the first user, the client device of the first user selects from among these client devices of the second user, during said step c), the one which is most capable of providing the first user with a service of reduced quality.

[0039] Thanks to these provisions, the first user can establish a session with the second user in the best possible conditions in practice, taking into account the service initially desired.

[0040] Correlatively, the invention relates to various devices.

[0041] It thus concerns, firstly, a client device, called the first user, of an IP network according to claim 7.,

[0042] The invention also relates, secondly, to a client device of a user, called second user, of an IP network, according to claim 8.

[0043] The advantages offered by these devices are essentially the same as those offered by the correlative methods briefly set out above.

[0044] It should be noted that it is possible to implement these devices in the context of software instructions and / or in the context of electronic circuits.

[0045] The invention also relates to a computer program downloadable from a communications network and / or stored on a computer-readable medium and / or executable by a microprocessor. This computer program is remarkable in that it comprises instructions for executing the steps of the selection method briefly set out above, when it is executed on a computer.

[0046] The advantages offered by this computer program are essentially the same as those offered by the said method.

[0047] Other aspects and advantages of the invention will become apparent upon reading the detailed description below of particular embodiments, given as non-limiting examples. The description refers to the accompanying figures, in which: there figure 1 schematically represents a system for the provision of multimedia services capable of implementing the invention, and the figure 2 schematically represents an embodiment of the invention in which a user A of an IMS network wishes to place an audio and video call to another user B of the same IMS network.

[0048] Although the present invention relates to IP networks in general, we will now consider, as an exemplary embodiment, an IMS type network architecture, as briefly presented above. This architecture is illustrated in the figure 1 .

[0049] The multimedia services offered by this IMS 1 network may include telephony, video telephony, content sharing services (“ content-sharing » in English), Presence, Instant Messaging, or television. These services are available to the user of a client device (" User Equipment », or UE in English) 10 belonging to the network 1, which allows the client device 10 to exchange multimedia streams and session control signals compliant with the SIP protocol, for example with the client device (not shown) of a user belonging to a SIP network (not shown) connected to the network 1.

[0050] The client device 10 may be a fixed or mobile terminal, or a home or business gateway, having SIP signaling means and possibly including means for rendering audiovisual content.

[0051] As shown in the figure 1 , this IMS 1 network includes, in addition to an IP transport infrastructure (not shown): at least one S-CSCF server; the S-CSCF server 27 manages in particular the procedure for registering devices connected to the network 1; the S-CSCF server 27 also manages the routing of the signaling between the client device 10 and the VM voicemail 25, Instant Messaging 26, and TAS telephony 29 servers; at least one I-CSCF server; the I-CSCF server 22 manages in particular the routing towards other terminals managed by the same IMS network 1 and the routing of the signaling between this IMS network 1 and other networks (not shown); at least one P-CSCF server; the P-CSCF server 21 serves as a connection entity between the IMS core network and the access network used by the client device 10; at least one database server, of the HSS type; the HSS server 24 contains the profile of the user of the client device 10 in terms of authentication data, location and subscribed services; at least one VM 25 voicemail server (" message-summary » in English); the VM server 25 manages the subscription of the client device 10 to the events of depositing / consulting messages intended for the client device 10, and notifies the client device 10 when these events occur; at least one Instant Messaging IM server 26; in the event of subscription by the user of the UE 10 to the Instant Messaging service, this user can dialogue “instantly” online with other subscribers to this service; and at least one telephony server TAS 29; the TAS server manages the telephone services to which the user of the terminal 10 has subscribed with his operator, such as number presentation or call forwarding.

[0052] Examples of Application Servers (AS) are the VM 25 voicemail, IM 26 instant messaging, and TAS 29 telephony servers.

[0053] Some services, such as those of the VM server 25 and the Instant Messaging server IM 26, rely on the terminal 10 subscribing to predetermined events, as explained above.

[0054] We will now describe, with reference to the figure 2 , several embodiments of the invention, in which it is assumed that a user A of an IMS network wishes to place, for example, an audio and video call to another user B of the same IMS network.

[0055] According to a first embodiment, the following steps are implemented.

[0056] During a step E1, the terminal of the first user A sends a SIP request of type OPTIONS to the second user B. This request includes a header (“ header» in English) containing an indicator according to the invention (which we will call “reversecap”); this indicator can, for example, be inserted in a “Require” header of the request.

[0057] As explained above with reference to the figure 1 , the request (OPTIONS in this case) sent by the terminal of the first user A is transmitted to the S-CSCF server (called S-CSCFA on the figure 2 ) in charge of the first user A, then to the I-CSCF server for routing to the S-CSCF server (called S-CSCFB on the figure 2 ) in charge of the second user B. The S-CSCFB server then transmits the request (mechanism of forking ) to all terminals of the second user B connected to the network (in this case, B1 to B4).

[0058] During a step E2, due to the presence in the request sent by the first user A of the “reversecap” indicator, each respective terminal of the second user B (i.e., from B1 to B4) responds to the OPTIONS request sent by the first user A by sending in turn to the first user A an OPTIONS request indicating the technical capabilities, and including a respective identifier (for example the classic label “+sip.instance”), of this respective terminal.

[0059] In a step E3, the terminal of the first user A analyzes the technical capability information contained in these OPTIONS requests, and selects one of them on the basis of this information and, optionally, predetermined criteria. Preferably, the terminal of the first user A selects the terminal of the second user B capable of providing an optimal service according to predetermined criteria; thus, in the present example, the terminal of the first user A could select the terminal B3, because this terminal (and it alone) is compatible with an HD audio and HD video session, in the case where these characteristics would be desirable for the first user A compared to a standard or low definition audio or video session.

[0060] In a step E4, the terminal of the first user A sends an INVITE request to the selected terminal (in this example, terminal B3), using, in this INVITE request, the label “+sip.instance” in a conventional manner to target the selected terminal.

[0061] Finally, during step E5, the terminal of the first user A and terminal B3 enter into an HD audio-video session.

[0062] According to a second embodiment, the following steps are implemented.

[0063] During a step E'1, the terminal of the first user A sends a SIP request of type INVITE to the second user B. This request includes a header containing the “reversecap” indicator according to the invention.

[0064] This request also mentions a service (in this example, an audio and video session) that user A wishes to obtain during the session being established. To do this, as defined in the IETF documents RFC 3840 and RFC 3841, the terminal of the first user A inserts, for example, in the "Contact" and "Accept-contact" headers of its request, the featuretag "audio" and the featuretag "video" designating the desired services. Similarly, where applicable, the featuretag "mmtel" would designate a telephone service, the featuretag "sip-im" would mean an instant messaging service, and so on.

[0065] In step E'2, the INVITE request sent by the terminal of the first user A is transmitted to the S-CSCFA server, then to the I-CSCF server, and finally to the S-CSCFB server. However, in accordance with the specifications of the IETF RFC 3841 document, the S-CSCFB server only transmits the request to the terminals of the second user B that are technically capable of an audio and video session; thus, terminals B2, B3 and B4 receive the request, but terminal B1 does not receive it because this terminal is technically capable of an audio session, but not of a video session.

[0066] During a step E'3, due to the presence, in the request sent by the first user A, of the "reversecap" indicator, each of the terminals of the second user B having received the INVITE request sent by the first user A (in this case, the terminals B2, B3 and B4) responds to the first user A by means of an OPTIONS type request indicating its technical capabilities.

[0067] Step E'4 is analogous to step E3 described above with reference to the first embodiment.

[0068] During step E'5, the terminal of the first user A responds: favorably (SIP response 200 OK) to the OPTIONS request sent by the selected terminal (B3 in the present example), which will continue to present the call (for example, call ringing), and unfavorably (for example, by means of an error code specific to the present invention) to the OPTIONS requests sent by the other terminals of the second user B (B2 and B4 in the present example), which then respond to the INVITE request received during step E'2 by indicating (for example, by means of a SIP code 487) that they are ending the current call.

[0069] It may be provided that, during the phase of selection of a terminal of the second user B, the terminals of the second user B having received the INVITE request during step E'2 ring, or on the contrary provide that they do not ring (for example upon detection of the presence of the "reversecap" indicator in the "Require" header) so that only the selected terminal will start ringing (after receipt of the 200 OK response sent by the first user A).

[0070] Finally, during a step E'6, the terminal of the first user A and the terminal B3 enter into an HD audio-video session.

[0071] According to a third embodiment, the following steps are implemented.

[0072] During a step E"1, the terminal of the first user A sends a SIP request of type INVITE to the second user B. This request mentions a service (in this example, an audio and video session) that user A wishes to obtain during the session being established, for example by inserting the featuretag "audio" and the featuretag “video” in the “Contact” and “Accept-contact” headers of its request.

[0073] But, unlike the first and second embodiments, this first request sent by the first user A does not contain an indicator according to the invention.

[0074] Step E"2 is analogous to step E'2 described above with reference to the second embodiment.

[0075] During a step E"3, the first user A receives “provisional” type responses (SIP codes 100 to 199) from each of the terminals of the second user B having received the INVITE request sent by the first user A (in this case, terminals B2, B3 and B4).

[0076] During a step E"4, the first user A sends a second SIP request, for example an UPDATE type request comprising a header containing the “reversecap” indicator according to the invention, or of a type (which will be called “REVOPTIONS”) specific to the present invention, to the terminals which responded to it (in this case, the terminals B2, B3 and B4).

[0077] During a step E"5, each of the terminals of the second user B having received the second request sent by the first user A (in this case, terminals B2, B3 and B4) therefore responds to the first user A by means of an OPTIONS type request indicating its technical capabilities.

[0078] Steps E"6 to E"8 are then implemented, which are respectively analogous to steps E'4 to E'6 described above with reference to the second embodiment.

[0079] In the example that has just been described according to three embodiments, it was assumed that not only were several terminals of the second user B capable of providing the service desired by the first user A, but that in addition one of these terminals (namely B3) was capable of providing a service of optimal quality (HD audio and HD video).

[0080] But in another case, it could naturally occur qu'aucun of the terminals of the second user B is not capable of providing the service desired by the first user A. It can be expected that, in such a case, the terminal of the first user A will select the terminal of B most capable of providing the first user A with a service of reduced quality, according to predetermined criteria. The terminal of the first user A is in fact capable of making this selection following receipt of the capabilities of the terminals B as described above.

[0081] Generally, the present invention can be implemented within the nodes of an IP network, for example client devices, by means of software and / or hardware components.

[0082] The software components may be integrated into a conventional computer program for managing a network node. Therefore, as indicated above, the present invention also relates to a computer system. This computer system conventionally comprises a central processing unit controlling a memory by signals, as well as an input unit and an output unit. In addition, this computer system may be used to execute a computer program comprising instructions for implementing any of the selection methods according to the invention.

[0083] Indeed, the invention also relates to a computer program downloadable from a communication network comprising instructions for executing the steps of a selection method according to the invention, when it is executed on a computer. This computer program can be stored on a computer-readable medium and can be executable by a microprocessor.

[0084] This program may use any programming language, and may be in the form of source code, object code, or code intermediate between source code and object code, such as in a partially compiled form, or in any other desirable form.

[0085] The invention also relates to an information medium, irremovable, or partially or totally removable, readable by a computer, and comprising instructions of a computer program as mentioned above.

[0086] The information carrier may be any entity or device capable of storing the program. For example, the carrier may include a storage medium, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording medium, such as a hard disk, or a USB flash drive (“ USB flash drive » in English).

[0087] On the other hand, the information carrier may be a transmissible carrier such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means. The computer program according to the invention may in particular be downloaded from a network such as the Internet.

[0088] Alternatively, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of any of the selection methods according to the invention.

Claims

1. Method of obtainment, by a first user of an IP network, of technical capabilities of a client device among a plurality of client devices of a second user, said client devices being connected to said IP network, said IP network implementing a session control protocol using signalling messages of request type and response type, said method comprising the following steps: a) a client device of said first user sends (E1, E'1, E"4) a said first signalling message of request type (INVITE, UPDATE, REVOPTIONS, OPTIONS) to said second user, said first message being of a dedicated type (REVOPTIONS) or comprising a header containing a dedicated indicator (reversecap), and b) each of the client devices of the second user having received said first message of a dedicated type (REVOPTIONS) or comprising a header containing a dedicated indicator (reversecap), responds (E2, E'3, E"5) to the first user by means of a said second signalling message of request type (OPTIONS) as a result of said dedicated type or of said dedicated indicator, said second message of request type indicating the technical capabilities of this client device of the second user and requesting delivery, by said client device of the first user, of the technical capabilities of this client device of the first user.

2. Obtainment method according to Claim 1, characterized in that it further comprises the following steps: c) after receipt of said second messages of request type (OPTIONS) sent by each of the client devices of the second user having received said first message of a dedicated type (REVOPTIONS) or comprising a header containing a dedicated indicator (reversecap), the client device of the first user selects (E'4, E"6, E3) one of these client devices of the second user on the basis at least of the technical capabilities contained in these second messages (OPTIONS), d) the client device of the first user sends (E4, E'5, E"7), to the selected client device, a favourable response (200 OK, INVITE) to the second message of request type (OPTIONS) sent in said step b) by this selected client device, and e) a session is set up (E5, E'6, E"8) between the client device of the first user and the selected client device.

3. Obtainment method according to Claim 2, characterized in that: - the second message of request type (OPTIONS) sent (E2) by each respective client device of the second user in said step b) comprises a respective identifier of this client device, and - the client device of the first user inserts (E4) the identifier of said selected client device into the response (INVITE) sent in said step d) to this selected client device.

4. Obtainment method according to Claim 2, characterized in that: - said first message of request type (INVITE) sent by the client device of the first user in said step a) mentions (E'1) a service that the first user desires to obtain during the session being set up, and - in said step d), the client device of the first user sends (E'5) an unfavourable response to the second messages of request type (OPTIONS) sent in said step b) by the client devices of the second user that are not selected.

5. Obtainment method according to Claim 2, characterized in that: - prior to said step a), the client device of the first user sends (E"1), to said second user, a message of request type (INVITE) mentioning a service that the first user desires to obtain during the session being set up, and - in said step d), the client device of the first user sends (E"7) an unfavourable response to the second messages of request type (OPTIONS) sent in said step b) by the client devices of the second user that are not selected.

6. Obtainment method according to Claim 2, characterized in that, if no client device of the second user having sent in said step b) a second message of request type (OPTIONS) indicating its technical capabilities is technically capable of delivering a service desired by the first user, the client device of the first user selects from these client devices of the second user, in said step c), the client device that is best able to deliver to the first user a service of reduced quality.

7. Client device of a user, called the first user, of an IP network implementing a session control protocol using signalling messages of request type and of response type, possessing: means for sending, to a second user of the IP network, a said first signalling message of request type (INVITE, UPDATE, REVOPTIONS, OPTIONS) of a dedicated type (REVOPTIONS) or comprising a header containing a dedicated indicator (reversecap), said dedicated type (REVOPTIONS) or dedicated indicator (reversecap) being capable of triggering a response to said first message, from each of the client devices of said second user having received said first message, by means of a said second signalling message of request type delivering its technical capabilities; means for receiving the second message of request type (OPTIONS) from each of the client devices of the second user having received the first message of request type, said second message of request type indicating the technical capabilities of said client device of the second user and requesting delivery, by said client device of the first user, of the technical capabilities of this client device of the first user; and means for, on the basis at least of said received information on technical capabilities, selecting one of the client devices of said second user having responded to the first message of request type and sending, to the selected client device of the second user, a favourable response (200 OK, INVITE) to said second message of request type received from this selected client device of the second user.

8. Client device of a user, called the second user, of an IP network implementing a session control protocol using signalling messages of request type and of response type, possessing means for: - receiving a said first signalling message of request type (INVITE, UPDATE, REVOPTIONS, OPTIONS) sent by a client device of another user, called the first user, of said IP network, said first message of request type being of a dedicated type (REVOPTIONS) or comprising a header containing a dedicated indicator (reversecap), and said dedicated type (REVOPTIONS) or dedicated indicator (reversecap) being capable of triggering a response to said first message, from each of the client devices of said second user having received said first message, by means of a said second signalling message of request type delivering its technical capabilities, - responding to said message of request type of dedicated type or comprising a header containing a dedicated indicator by sending a said signalling message of request type (OPTIONS) as a result of said dedicated type or of said dedicated indicator, said signalling message of request type indicating its technical capabilities and requesting delivery, by said client device of the first user, of the technical capabilities of this client device of the first user.

9. Fixed or partly or fully removable data storage means including computer program code instructions for executing the steps of an obtainment method according to any one of Claims 1 to 6.

10. Computer program downloadable from a communications network and / or stored on a computer-readable medium and / or able to be executed by a microprocessor, characterized in that it comprises instructions for executing the steps of an obtainment method according to any one of Claims 1 to 6 when it is executed on a computer.